Hi Claus, we are having a similar problem.
Our configuration is: - Camel 2.10.1 - ActiveMQ 5.5.1 > In Camel 2.9 you can use replyToType=Exclusive, which would then not have this leak. We cannot use replyToType=Exclusive because we are using a cluster environment, so we have to use shared reply queues. > The leak is possible to be fixed on the AMQ side, I will keep looking into > this. Do you know if this problem was solved in some new version of ActiveMQ? Thanks, Ana -- View this message in context: http://camel.465427.n5.nabble.com/Possible-memory-leak-in-org-apache-activemq-pool-PooledSession-tp4964951p5723614.html Sent from the Camel - Users mailing list archive at Nabble.com.
