[
https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203544#comment-15203544
]
Keith Wall commented on QPID-7155:
----------------------------------
The ServerIdleReadTimeoutTicker requires that the peer produces bytes. If it
receives nothing then it is required to close the connection. The issue here
is that the broker/client have not yet negotiated heartbeating so the peer
(client) is entitled to let the line fall silent. I think it is unreasonable
for the Broker to have the ServerIdleReadTimeoutTicker installed before
connection tune has agreed the heartbeat parameters.
I think we should have a ticker dedicated to ensuring peers send a protocol
header in a timely manner, then we should rely solely on the
{{SlowConnectionOpenTicker}} to ensure that the connection becomes open with a
second timely period.
> [Java Broker] Idle timeout ticker times out connection before heartbeating is
> negotiated
> ----------------------------------------------------------------------------------------
>
> Key: QPID-7155
> URL: https://issues.apache.org/jira/browse/QPID-7155
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
> Attachments:
> TEST-org.apache.qpid.client.failover.MultipleBrokersFailoverTest.testFailoverOnBrokerStop.txt
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
