-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
connection manager stop trying to reconnect after connection failed #310
Comments
Any news about the issue? |
It should keep reconnecting until you ask it to stop. If you suspect this is because of some kind of ordering-of-connects-and-disconnects problem, I'd suggesting trying to add a unit test to this project that recreates it. If you can figure out a way to recreate this, I'd be interested in that too. |
I will try to reproduce it with a unit test and update here if I am able to. |
For a while, we've been dealing with the same problem: getting stuck when trying to reconnect on an unreliable network. It seems that by setting a timeout value in the options like this: From what I understand now, the default node.js In my opinion, it's best practice to always configure this timeout. I believe it would be beneficial to emphasize this point in the library documentation. Any way, thanks for a great library! @jwalton |
We had an issue that we are currently unable to reproduce with a device that was under a low network,
The device had 10 disconnection events that were followed up by a successful reconnection,
but then on the 11
disconnect
, even the device receivedconnectFailed
event and then did not try to reconnect anymore, does aconnectFailed
not lead to a reconnection attempt? is this is a know issue?Version:
4.1.6
amqp version:
0.10.1
code of reconnect mechanism:
Logs:
The text was updated successfully, but these errors were encountered: