Conclusion: I have solved the issue few days ago by using Spring CachingConnectionFactory which wraps MQQueueConnectionFactory - I was aware of this possibility but I could not believe it can create memory leak. I still don´t understand it and IMO this is bug (MQ?).
-- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-memory-leaking-with-IBM-MQ-tp5751442p5751590.html Sent from the Camel - Users mailing list archive at Nabble.com.
