Hi, I just found out that due to the mode I started my app in my class path were both camel jars ( old ones and camel-1.4.0 ) and my application loaded at runtime the old jars.
So it's possible that camel-1.4 does not have this problem anymore but unfortunately we ditched the camel jms component and turned to direct spring message listeners so when I have some time I will revert the configration and let you know if the problem is still there. Regards, Horia Claus Ibsen wrote: > > Hi > > I recall there was a issue like this 1-2 months ago. Try searching the > user and dev forums. > > Can you try with activeMQ instead of WebSphereMQ to see if it has the same > issue? We would like to narrow it down what is the problem. > > > Med venlig hilsen > > Claus Ibsen > ...................................... > Silverbullet > Skovsgårdsvænget 21 > 8362 Hørning > Tlf. +45 2962 7576 > Web: www.silverbullet.dk > > -- View this message in context: http://www.nabble.com/DefaultMessageListenerContainer-threading-issue-tp18811410s22882p18866902.html Sent from the Camel - Users mailing list archive at Nabble.com.
