camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: How many JMS transactions within a route?
Date Mon, 10 Aug 2015 20:11:11 GMT
You can read more about the supported cache options here [1], but
CACHE_CONSUMER is the best option in your case.
XA is not needed, because you only interact with one resource/broker.
I'm not sure whether we have to have two JMS sessions here. May be an JMS
expert can answer this question...




Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

On Mon, Aug 10, 2015 at 3:35 AM, kov <> wrote:

> 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:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message