Hi My understanding is that the JMS connection factories were built for use in a J2EE container and if you are using them outside of one, which sounds like you are, then it must be wrapped in either Spring's CachingConnectionFactory or ActiveMQ's PooledConnectionFactory. Though I have read in places that if you're purely consuming from JMS then it's not strictly needed, I haven't tested this myself so don't know if it's true. However there is no harm wrapping it up regardless.
On 27/05/2014, at 7:40 AM, Paolo28 <paolo.sa...@gmail.com> wrote: > 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.
