Claus Ibsen-2 wrote: > > Can you post a bit more on the stacktrace? Maybe we can find a spot in > the camel-jms component to workaround this issue by setting an non > null message on the JmsException. This may help prevent this spring > bug. >
Hi Claus, That was the entire stack trace I'm afraid! BTW: Is there a big issue with regards to upgrading Camel to Spring 3? Kind regards, Christopher -- View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510888.html Sent from the Camel - Users mailing list archive at Nabble.com.
