[
https://issues.apache.org/jira/browse/QPID-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767281#action_12767281
]
Martin Ritchie commented on QPID-2154:
--------------------------------------
After taking a heap dump. Out of the many(15) virtualhosts that we have
created! (Something else to address with our InVM testing)
There is only one virtualhost that has eny AMQProtocolEngines. This Engine is
marked _closed=true, so wlll never remove from the _registry.
Questions:
- The only place _closed is set true is AFTER the ConnectionRegistry remove..
so was it added twice?
- If it wasn't added twice then why was it not removed.
> New Network IO Layer has doesn't appear to clean up connections on connection
> close.
> ------------------------------------------------------------------------------------
>
> Key: QPID-2154
> URL: https://issues.apache.org/jira/browse/QPID-2154
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Fix For: 0.6
>
> Attachments: MessageDisappearTail.txt
>
>
> The new AMQProtocolEngine appears does not appear to reliably clear the
> ConnectionRegistry when closing connections.
> The Missing test run over the weekend genereated 25GB of log which appears to
> be the Broker stuck in the ConnectionRegistry.close() loop. This would
> suggest that the new IO layer is not correctly notifying and/or removing the
> closed connection from the ConnectionRegistry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
