[ https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235475#comment-15235475 ]
ASF subversion and git services commented on QPID-7155: ------------------------------------------------------- Commit 1738607 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1738607 ] QPID-7155: [Java Broker] Change ticker implementation to separate slow protocol header detection from reader/writer idle timeouts established by connection tune > [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 > Fix For: qpid-java-6.0.2, qpid-java-6.1 > > Attachments: > 0001-QPID-7155-Java-Broker-Change-ticker-impl-to-separate.patch, > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org