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
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||2.9.0 [ 12316374 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|21h 29m||1||Claus Ibsen||11/Nov/11 08:34|