You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2014/05/30 17:45:03 UTC
[jira] [Commented] (QPID-5795) Closing a connection leaks a
ConnectionAdapter object
[ https://issues.apache.org/jira/browse/QPID-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013824#comment-14013824 ]
Keith Wall commented on QPID-5795:
----------------------------------
I suspect that QPID-5763 might be invalid.
> Closing a connection leaks a ConnectionAdapter object
> -----------------------------------------------------
>
> Key: QPID-5795
> URL: https://issues.apache.org/jira/browse/QPID-5795
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.29
> Reporter: Keith Wall
> Assignee: Keith Wall
>
> We currently have a regression on trunk (0.29) whereby closure of a messaging connection (any AMQP version) causes a ConnectionAdapter object to be leaked.
> On connection close (normal or otherwise), the code fails to arrange for the reversal of ACO#registerChild, therefore the maps ACO#_childrenByName etc permanently retain the reference to the ConnectionAdapter. The leak is large because this causes the sizeable IO buffers to be retained too.
> This causes any long running test, that creates and closes many connections over the lifetime of the Broker to run the risk of OOM. This problem has been noticed owning to the failure of the long running TCK test (which has been failing with OOM).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org