Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Recently, MultipleBrokersFailoverTest#testFailoverOnBrokerStop failed. Log attached.
Analysis has shown the following sequence of events:
- 01:58:24,044 broker receives connectionStartOk
- 01:58:25,894 broker sends connectionSecure
- 01:58:26,010 broker times out the connection
- 01:58:26,061 client tries to send connectionSecureOk
The problem seems to be that the ServerIdleReadTimeoutTicker times out the connection even though the broker is the one being slow and heartbeating not being negotiated yet.