Ah :) BTW if you're not using Spring 2.5.1, its well worth explicitly setting CACHE_CONSUMER when using JMS consumption; as it avoids having to start/stop JMS connections/sessions/consumers under the covers. (Due to a spring bug in previous releases with transactions, we had to default to CACHE_CONNECTION).
On 29/02/2008, Sigmund <[EMAIL PROTECTED]> wrote: > > > Sigmund wrote: > > > > Since yesterday we've been experiencing serious problems with the latest > > camel snapshot. > > The activemq connection goes up and down. We are currently using vm:// > > transport and > > amq 5.1-SNAPSHOT. Didn't get camel 1.2 and amq 5.0.0 to work.. > > > > Please heeeelp > > > > /S > > > > Stacktrace: > > > ... > > > > > > > Solved by removing activemq-data folder created on the appserver :-) > Our previous release worked without doing that, weeird.. > > /S > > -- > View this message in context: > http://www.nabble.com/Show-stopping-problems-in-camel-1.3-SNAPSHOT%2C-transport-disposed-tp15754942s22882p15757240.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
