[CAMEL-4657] camel-jms - Request/Reply - Leak in ActiveMQSessionPool causing it to eat up memory, when using fixed replyTo queue names

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Component/s: camel-jms
• Labels: activemq
• Estimated Complexity: Advanced
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 10/Nov/11 11:05
• Updated: 11/Nov/11 08:34
• Resolved: 11/Nov/11 08:34

Description

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

Issue Links

• depends upon: AMQ-3588 PooledSession - Can cause memory leak in case many consumers is created by the session