Taking the example of a JMS-based application that processes messages from a
JMS message bus:
<camelContext...>
<route id="step1">
<from uri="msgbus:q1" />
<transacted />
<to uri="msgbus:q2" />
</route>
</camelContext>
* The 'msgbus' token refers to a JmsComponent with a
CachedConnectionFactory and cache level=CACHE_CONSUMER.
What is the expected number of JMS-transactions for the <from> and <to>
endpoints? Playing with this example, it appears that each of the endpoints
gets a separate JMS-transaction. Does anybody know if that is the case? Are
there design or other reasons for that, maybe enabling further options I
haven't considered? Would it be possible for the route to use one
JMS-transaction for both the consume and send? Or would you have to use XA
transactions to make that happen?
--
View this message in context:
http://camel.465427.n5.nabble.com/How-many-JMS-transactions-within-a-route-tp5770390.html
Sent from the Camel - Users mailing list archive at Nabble.com.
