After some diggin in the spring docs i came up with a replacement for the jcaPooledConnectionFactory that should support consumer pooling: Springs CachingConnectionFactory. There are some restrictions, see http://tmielke.blogspot.de/2012/03/camel-jms-with-transactions-lessons.html <http://tmielke.blogspot.de/2012/03/camel-jms-with-transactions-lessons.html> , but this is no problem in my case. The only remaining question is does this support autoenlistment of a named xa datasource with the tx manager?
-- View this message in context: http://camel.465427.n5.nabble.com/JMS-XA-component-with-a-maxConcurrentConsumers-value-1-tp5734666p5734679.html Sent from the Camel - Users mailing list archive at Nabble.com.
