[
https://issues.apache.org/jira/browse/CAMEL-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4657.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.9.0)
This was a bug in ActiveMQ which has been fixed in the upcoming AMQ 5.6 release.
> camel-jms - Request/Reply - Leak in ActiveMQSessionPool causing it to eat up
> memory, when using fixed replyTo queue names
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4657
> URL: https://issues.apache.org/jira/browse/CAMEL-4657
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Labels: activemq
>
> See nabble
> http://camel.465427.n5.nabble.com/Possible-memory-leak-in-org-apache-activemq-pool-PooledSession-tp4964951p4964951.html
> This bug is in ActiveMQ, but creating a ticket to get it resolved as the leak
> is apparent when using Spring DMLC with CACHE_SESSION, which Camel by default
> does when doing request/reply over JMS with fixed replyTo queues.
> Then the consumer is not cached, and therefore created on each poll, but the
> ActiveMQSessionPool keeps growing in its internal list of created consumers,
> as the session is cached.
> Most likely a patch is needed to fix this in the AMQ side
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
