[
https://issues.apache.org/jira/browse/AMQ-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443054#comment-13443054
]
Claus Ibsen commented on AMQ-3997:
----------------------------------
The issues was brought to my attention from this forum thread, which we got
notified about on the Camel @dev list
http://forum.springsource.org/showthread.php?128152-Spring-Integration-2-1-request-reply-benchmark-tests-showed-very-poor-performance
Running the sample code, will cause the memory issue. However switching to use
a Spring based Cached connection factory, causes no problem, and has no memory
leaks. But using the AMQ pool instead causes the leak.
> 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
> Fix For: 5.7.0
>
>
> 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
