[
https://issues.apache.org/jira/browse/QPID-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPID-7011.
------------------------------
Resolution: Invalid
Investigation of the problem revealed that it is not a broker issue but a
client one. It was caused by direct memory usage on the client. The GC
collections were taking 5-10 seconds due to finalization of direct byte
buffers. Switching back to usage of heap byte buffers in commit
[https://svn.apache.org/r1727449] resolved the issue
> [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) on sending ConnectionStart (It looks like created ConnectionStart frame is
> not put onto wire)
> {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: [email protected]
For additional commands, e-mail: [email protected]
