I just checked the change log of Camel 2.7.0[1], and didn't find any jms
related change that could cause this kind of issue.
As Camel 2.7.0 moved to Spring 3.x, can you check if your ActiveMQ run
time is still using Spring 2.x ?
[1]https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&styleName=Html&version=12316021
On 3/30/11 3:14 AM, Jason Chaffee wrote:
Confirmed that the only changes are camel jars.
camel-core
camel-jms
camel-spring
camel-xstream
We went from 2.6.0 --> 2.7.0
It works in 2.6.0, but not 2.7.0.
This is definitely a bug introduced by camel-2.7.0.
Jason
-----Original Message-----
From: Jason Chaffee [mailto:[email protected]]
Sent: Sunday, March 27, 2011 11:15 PM
To:[email protected];[email protected]
Subject: RE: 2.7.0 changes
Nope. The only change was camel the camel version and when I went back
to 2.6.0 and everything worked again.
This is definitely an issue with the 2.7.0 version of camel. I will
check the other dependencies and see if camel 2.7.0 introduced something
that was picked up transitively.
-----Original Message-----
From: Richard Kettelerij [mailto:[email protected]]
Sent: Sat 3/26/2011 4:41 AM
To:[email protected]
Subject: Re: 2.7.0 changes
Indeed, I've noticed the ActiveMQ ShutdownHook in your logs. At first
glance
it seems to me this is an issue with ActiveMQ (not Camel). Have you
changed
ActiveMQ version between 2.6 and 2.7? You can try asking the ActiveMQ
guys (
http://activemq.apache.org/discussion-forums.html).
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
