Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Fixed issue with reconnect mechanism #251
We are sort of in luck. The issue will only occur if the auth changes while a connection has been made. In the case the auth is refused while calling
Now if the authentication changes while the connection is established, RabbitMQ 3.1.x does nothing to the connection. The established connections can still publish and consume.
Interestingly in my test when the connection drops and the reconnect kicks in it reconnects without any auth issue :/ Is the auth cached in some way?