On Wed, Jun 23, 2010 at 1:57 PM, huntc <hu...@mac.com> wrote: > > > 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? >
I think we can fix the issue with a custom exceptionListener which fixes the null message. Can you test it by creating a custom javax.jms.ExceptionListener class and then set the message to a non null value. And in Camel you can register the listener using the exceptionListener=#myListener configuration in the endpoint uri. If it fixes it we can create a listener to be shipped out of the box. > 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. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
