You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2016/01/21 11:51:39 UTC
[jira] [Updated] (QPID-7011) [Java Broker] Broker can run into
conditions when receiving of initial protocol exceeds the handshake timeout
and connection is closed due to inactivity
[ https://issues.apache.org/jira/browse/QPID-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-7011:
-----------------------------
Description:
On running performance tests for 0-9 protocol the tests can fail due to initial protocol receiving (or receiving of ConnectionStartOk) takes more time then default handshake timeout (2seconds). The issue occurs for the subsequent tests running after other tests which had cleared their test objects (queues/bindings/messages). It never happens for the first test.
On broker side connections can be forcibly closed due to inactivity in 2 ways:
1) on not receiving of initial protocol
{noformat}
2016-01-20 18:51:26,209 INFO [IO-/127.0.0.1:39254] (q.m.c.idle_close) - [Broker] CON-1003 : Closed due to inactivity
{noformat}
2) after sending ConnectionStart but not receiving ConnectionStartOk during initial handshake interval
{noformat}
2016-01-20 18:51:26,338 INFO [IO-/127.0.0.1:39236] (q.m.c.idle_close) - [con:482(/127.0.0.1:39236)] CON-1003 : Closed due to inactivity
{noformat}
was:
On running performance tests for 0-9 protocol the tests can fail due to initial protocol receiving (or receiving of ConnectionStartOk) takes more time then default handshake timeout (2seconds). The issue occurs for the consequence tests running after other tests which had cleared their test objects (queues/bindings/messages). It never happens for the first test.
On broker side connections can be forcibly closed due to inactivity in 2 ways:
1) on not receiving of initial protocol
{noformat}
2016-01-20 18:51:26,209 INFO [IO-/127.0.0.1:39254] (q.m.c.idle_close) - [Broker] CON-1003 : Closed due to inactivity
{noformat}
2) after sending ConnectionStart but not receiving ConnectionStartOk during initial handshake interval
{noformat}
2016-01-20 18:51:26,338 INFO [IO-/127.0.0.1:39236] (q.m.c.idle_close) - [con:482(/127.0.0.1:39236)] CON-1003 : Closed due to inactivity
{noformat}
> [Java Broker] Broker can run into conditions when receiving of initial protocol exceeds the handshake timeout and connection is closed due to inactivity
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7011
> URL: https://issues.apache.org/jira/browse/QPID-7011
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.1
> Reporter: Alex Rudyy
>
> On running performance tests for 0-9 protocol the tests can fail due to initial protocol receiving (or receiving of ConnectionStartOk) takes more time then default handshake timeout (2seconds). The issue occurs for the subsequent tests running after other tests which had cleared their test objects (queues/bindings/messages). It never happens for the first test.
> On broker side connections can be forcibly closed due to inactivity in 2 ways:
> 1) on not receiving of initial protocol
> {noformat}
> 2016-01-20 18:51:26,209 INFO [IO-/127.0.0.1:39254] (q.m.c.idle_close) - [Broker] CON-1003 : Closed due to inactivity
> {noformat}
> 2) after sending ConnectionStart but not receiving ConnectionStartOk during initial handshake interval
> {noformat}
> 2016-01-20 18:51:26,338 INFO [IO-/127.0.0.1:39236] (q.m.c.idle_close) - [con:482(/127.0.0.1:39236)] CON-1003 : Closed due to inactivity
> {noformat}
--
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