Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Failure Detection has a possibility to a race condition with the processing of the client packets (or frames in the case of AMQP).
This is because Netty detects the failure and removes the connection objects while the packets are still processing things.
I was not able to reproduce this particular issue, but I have seen a case from a memory dump where the consumer was created while the connection was already dropped, leaving the consumer isolated without any communication with clients.
That particular case I could see a possibility because of these races.
I am adding tests to exercise connection failure in stress and I was able to reproduce other issues.
