Connection troubleshoot

Hello. I made some tests and apparently the connection cannot be completed if I try to create a new one right after opening the program and after to connect to my previous session (automatically).

This picture shows the logging (uncomlete image for security reasons) and this connection spend almost 2 minutes to stabilish. Using the mongo tool it spend few milliseconds!

I wan't to help but there is no more information =/

Thanks.

Thank you for your feedback.

Unfortunately, I can't reproduce the problem locally. If possible, could you give me the complete steps to reproduce it

I made a blurred version of a heavy utilization of the NoSqlBooster. I think this will not help enough because of the blurry itself, but we can talk more about issues I found: https://youtu.be/QlaIrEvTY0o

The major part of the video shows connections (the connection itself or two clicks in a single collection or clicking to show the collection statistics) getting timeout.

Every time I connected to the database directly in the mongo shell. Once I even connected to all replica sets (with blurred screen) to show the replica statuses and oplog times.

All my replica sets are being monitored by Mongo Cloud Manager and I have not even one network or replication problem.

I think also the Replica read mode doesn't are working fine. I don't know what NoSqlBooster do different in those modes, but one replica set of mine connected with the secondary preferred read mode but didn't connected with the secondary.

A weird bug happened in 8:20 - The first two click in the collection doesn't worked (connection timeout). When I clicked run manually in the same editor, it runs but don't returned any document (isn't an empty collection). The second two click on the same collection doesn't work either, but running manually the script returned documents with the right response. The error in 6:15 is about the same thing. A red error saying the collection doesn't exists (in the admin) appeared, but I was trying to connect to a collection in another database.

I notice the description on the editor (with collection and database) was showing admin database for the first two clicks, but this is not the admin database.

Sorry for blurred screens but some information in those collection cannot be distributed.

I want NoSqlBooster to be great because I really like this tool, but me and many friends had those network issues. I also saw the log info and there is no information about connection issues.

I think you guys need multiple replica sets (not local machines) to make some stress test on the application... Creating connections, running scripts, closing connections, making all those many and many times in a row. I have like 100 mongo instances and I think this why I have so many problems with NoSqlBooster.

Thanks and I make myself available for testing any solution you guys can provide, even with my restricted time (this the reason I don't even tried to blurry only private information and maybe restricted more than needed).