Thanks; to be clear, I'd prefer not to use an XA transaction here, but I'd also like to consume from q1 and publish to q2 in a single transaction, that's why I asked if an XA transaction was the only choice, even when I'm communicating over a single JMS message bus.
Mostly just trying to understand what the expected behavior with that configuration is, and what my options for altering it are? Right now, it seems that when a route gets built that references my JMSComponent, a session is requested from the JMSComponent which just caches one for each consumer. This ends up with a session for the consumer of q1, and a distinct session for the publisher to q2. Is that pretty much how it works? Just wondering what variations on caching behavior exists. Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/How-many-JMS-transactions-within-a-route-tp5770390p5770502.html Sent from the Camel - Users mailing list archive at Nabble.com.
