Mongobooster creates too many connections on Atlas
Solved
Hi,
I have a paid version of mongobooster version 3.5.6
On our production database (3 replicas) that is hosted on Atlas we reached 350 connections all from mongobooster within 1 minute.
This lead to a crash of the application.
Is there any known issue about this ?
The same problem 
Thank you for your feedback.
We reviewed the related code. There may be a potential error with db.close in the finally block.
I have worked out a new build to try to resolve it. could you please download and give it a try.
http://s3.mongobooster.com/download/3.5/mongobooster-3.5.7-hotfix2.dmg
Thank you for your feedback.
We reviewed the related code. There may be a potential error with db.close in the finally block.
I have worked out a new build to try to resolve it. could you please download and give it a try.
http://s3.mongobooster.com/download/3.5/mongobooster-3.5.7-hotfix2.dmg
Had the same issue. Quitting the app, or Disconnecting from each hosts and then quitting the app left few:
running each time. The # of opened connections on our servers kept growing overtime.
With version (mongobooster-3.5.7-hotfix2.dmg), this behaviour is gone. All connections are properly closed.
Thanks.
Had the same issue. Quitting the app, or Disconnecting from each hosts and then quitting the app left few:
running each time. The # of opened connections on our servers kept growing overtime.
With version (mongobooster-3.5.7-hotfix2.dmg), this behaviour is gone. All connections are properly closed.
Thanks.
Just observed the same but with rebranded version
/Applications/NoSQLBooster for MongoDB.app/Contents/Resources/app.asar/backend/sshConnection left after what seemed to be a graceful client shutdown.
Just observed the same but with rebranded version
/Applications/NoSQLBooster for MongoDB.app/Contents/Resources/app.asar/backend/sshConnection left after what seemed to be a graceful client shutdown.
Replies have been locked on this page!