Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
M2, M2.1, M3, M4, 0.5
-
None
Description
If the broker closes the connection as a result of an erroneous object creation on the session. Such as creating to many sessions or creating a queue with invalid properties then it will appear to hang from the clients PoV.
What is happening?
The broker closes the connection, so the client attempts failover, but the last action that caused the error is already recorded so on establishing the new sessions failover occurs again. This repeats infinitely.
The Failvover properties cannot help here as the Connection was successfully made and so the looping/retry values have been reset.