bugfix of connection full, see #322 and #346 .
Here is a brief of my modification:
liveSockets means unused connections and used connections, unusedSockets means unused connections. However, a connection won't be released even if it's an "unused" connection. So this comparison only restricts the used connections but not the total connections.
So in my understanding, this comparison(len(server.liveSockets)-len(server.unusedSockets) >= poolLimit) can only limit the total connections but not used connections. The right comparison should be: len(server.liveSockets) >= poolLimit && len(server.unusedSockets) == 0。
This modification has already been merged and verified in my mgo branch which is used in MongoShake tools.
bugfix of connection full, see #322 and #346 . Here is a brief of my modification:
liveSocketsmeans unused connections and used connections,unusedSocketsmeans unused connections. However, a connection won't be released even if it's an "unused" connection. So this comparison only restricts the used connections but not the total connections. So in my understanding, this comparison(len(server.liveSockets)-len(server.unusedSockets) >= poolLimit) can only limit the total connections but not used connections. The right comparison should be:len(server.liveSockets) >= poolLimit && len(server.unusedSockets) == 0。 This modification has already been merged and verified in my mgo branch which is used in MongoShake tools.