I am using the config for jms xa transactions from the following website: https://access.redhat.com/site/documentation/en-US/Fuse_ESB_Enterprise/7.1/html/EIP_Transaction_Guide/files/XaJms-Sample.html <https://access.redhat.com/site/documentation/en-US/Fuse_ESB_Enterprise/7.1/html/EIP_Transaction_Guide/files/XaJms-Sample.html>
The jms component property maxConcurrentConsumers defaults to 1, and in every example i look this holds true. Are there any consequences if i crack it up? I guess every consumer thread gets its own transactional context? -- View this message in context: http://camel.465427.n5.nabble.com/JMS-XA-component-with-a-maxConcurrentConsumers-value-1-tp5734666.html Sent from the Camel - Users mailing list archive at Nabble.com.
