Avoid trapped in db connecting state if mistakenly call db.open first and server connect afterward. #3
Avoid trapped in db connecting state if mistakenly call db.open first and server connect afterward. #3kenspirit wants to merge 1 commit intochristkv:masterfrom kenspirit:master
Conversation
… and server connect afterward. Client insert command will keep pushing to commands list if db._state is always connecting and set to autoreconnect.
|
Why are you calling db.open and server.connect. Server connect should never be called by your code |
|
Hi Christian, Thanks for confirming me that Server connect should never be called by our I think I might also submit fix to them or notify the owner. BTW, I would like to ask you a question regarding what is the most I think then we should wrap the nodejs app server startup in the callback But I saw another reply in I wonder whether the document for nodejs-mongodb-native should document On Tue, Dec 4, 2012 at 6:53 AM, Christian Amor Kvalheim <
Ken Chen |
|
Hello I have installed on my system. Can you guide me what i am doing wrong? |
Avoid trapped in db connecting state if mistakenly call db.open first and server connect afterward.
Client insert command will keep pushing to commands list if db._state is always connecting and set to autoreconnect.
Line 1886 in db.js method Db.prototype._executeInsertCommand:
if(self._state == 'connecting' && this.serverConfig.autoReconnect)