May be we shoud use CACHE_NONE when using JmsTransactionManager so that it
creates a new connection/session/consumer for every message? That's bad!
-- 
View this message in context: 
http://www.nabble.com/JmsComponent-issue-with-spring%27s-JmsTransactionManager-is-used-tp21697364s22882p21698182.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to