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 2016/01/08 14:28:39 UTC

[jira] [Closed] (QPID-6951) [Java Client] AMQSession.deregisterConsumer() leaks Memory

     [ https://issues.apache.org/jira/browse/QPID-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall closed QPID-6951.
----------------------------

> [Java Client] AMQSession.deregisterConsumer() leaks Memory
> ----------------------------------------------------------
>
>                 Key: QPID-6951
>                 URL: https://issues.apache.org/jira/browse/QPID-6951
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.18, 0.22, 0.32, qpid-java-6.0
>            Reporter: Lorenz Quack
>            Assignee: Keith Wall
>             Fix For: qpid-java-6.0.1, qpid-java-6.1
>
>         Attachments: QPID-6951-fix.diff
>
>
> If a JMS user continually closes consumers on the same transactional session, a memory leak occurs at the following location.  The leak remains until the Session is closed ({{Session#close()}}) or the session is rolled-back. ({{Session#rollback()}}).
> {{AMQSession.deregisterConsumer()}} contains the following code:
> {code}
> if (_transacted)
> {
>     _removedConsumers.add(consumer);
> }
> {code}
> However, the {{_removedConsumers}} list is only cleaned up on rollback and nowhere else.
> This leak appears to be longstanding.  It looks like it was added at M3 (QPID-832). 



--
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