Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Chat not working with mongodb replicaSet



Error when initiating a chat with MongoDB replica connection string. When the primary database stops, the chat also stops and does not swap to the secondary database. This behavior occurs when the primary MongoDB details (only) are provided.

Note: MongoDB replica works fine.

Error Messages

'MongoError: seed list contains no mongos proxies, replicaset connections requires the parameter replicaSet to be supplied in the URI or options object, mongodb://server:port/db?replicaSet=name',
' at connectCallback (/home/ec2-user/Installables/chat/server/node_modules/connect-mongo/node_modules/mongodb/lib/mongo_client.js:422:23)',
' at /home/ec2-user/Installables/chat/server/node_modules/connect-mongo/node_modules/mongodb/lib/mongo_client.js:333:11',
' at nextTickCallbackWith0Args (node.js:420:9)',
' at process._tickCallback (node.js:349:13)']

Steps to Reproduce

  1. Configure a MongoDB to work in a replica set of one primary and one secondary database.
  2. Integrate the MongoDB with the chat.

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-37159.

Published December 3, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us