qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7155) [Java Broker] Idle timeout ticker times out connection before heartbeating is negotiated
Date Tue, 12 Apr 2016 12:09:25 GMT

    [ https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237052#comment-15237052
] 

ASF subversion and git services commented on QPID-7155:
-------------------------------------------------------

Commit 1738786 from orudyy@apache.org in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1738786 ]

QPID-7155: [Java Broker] Change ticker implementation to separate slow protocol header detection
from reader/writer idle timeouts established by connection tune

          Merged from trunk with manual confict resolution 
          svn merge -c 1738607  ^/qpid/java/trunk

> [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
>            Assignee: Alex Rudyy
>            Priority: Minor
>             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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message