You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2012/08/28 14:24:07 UTC

[jira] [Resolved] (AMQ-3997) Memory leak in activemq-pool

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

Gary Tully resolved AMQ-3997.
-----------------------------

    Resolution: Fixed

Patch applied with thanks in http://svn.apache.org/viewvc?rev=1378098&view=rev
                
> Memory leak in activemq-pool
> ----------------------------
>
>                 Key: AMQ-3997
>                 URL: https://issues.apache.org/jira/browse/AMQ-3997
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0
>            Reporter: Claus Ibsen
>            Assignee: Gary Tully
>              Labels: leak
>             Fix For: 5.7.0
>
>         Attachments: AMQ-3997.patch, bad.png, good.png
>
>
> The org.apache.activemq.pool.PooledConnectionFactory from activemq-pool has a severe memory leak when using it for sending a lot of messages. Over time this causes memory to be eaten up.
> I have tracked it down to the following tickets:
> - AMQ-3680, which keeps adding event listeners, despite previously added
> - AMQ-2643, code which keep track of loaned sessions, causing JVM to create too many ConcurrentLinkedQueue$Node instances
> There may be others. But with resolutions to those I can get the pool to not eat memory, and keep memory consumption low.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira