Hi,
James.Strachan wrote: > > BTW a side point - by default Camel uses the CACHE_CONNECTION level > with the MessageListenerContainer due to this spring bug... > > http://www.nabble.com/please-vote-for-SPR-3890-to-improve-Camel%27s-JMS-support-for-both-JMS-transactions-and-efficiency-tf4626284s22882.html#a13210354 > > This unfortunately causes sessions and consumers to be created, used > for one message and then stopped again (which typically causes a new > thread to be created for the consumption of the message then its > closed again). > > You can switch to using CACHE_CONSUMER which should help - it'll then > reuse the same threads/sessions/consumers. The downside though is that > due to the Spring bug mentioned above, you can't consume from JMS and > send to another JMS destination in a single JMS transaction. > thank you this was exactly the point. So we have to wait for the spring guy's to fix it? Or is there any possibility to receive the fix in advance? kind regards Oliver -- View this message in context: http://www.nabble.com/Camel-keeps-adding-and-removing-Consumers-when-using-DefaultMessageListenerContainer-tf4778316s22882.html#a13742794 Sent from the Camel - Users mailing list archive at Nabble.com.
