I was using Camel 2.2.0 so I've now upgraded to 2.3.0 in the hope that the problem may go away.
My other thought is to upgrade the camel-activemq component. I noticed that I'm using activemq-camel:5.2.0 as per the doco. and that this brings in activemq-core:5.2.0 and activemq-pool:5.2.0. This is obviously behind the current release of AMQ which is 5.3.2, so I'm wondering if there have been fixes around that. If my Camel upgrade doesn't look to have effected the problem then I'll bring in activemq-*:5.3.2 and see if that makes a difference. Any other pointers greatly appreciated of course. -- View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510288.html Sent from the Camel - Users mailing list archive at Nabble.com.
