camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <>
Subject please vote for SPR-3890 to improve Camel's JMS support for both JMS transactions and efficiency
Date Mon, 15 Oct 2007 10:44:26 GMT
For a background to the problem see this issue

Basically we can't use efficient JMS consumption (using CACHE_CONSUMER
level of caching) with spring's MessageListenerContainer while at the
same time using a single JMS transaction to do things like


We've erred on the side of caution so that Camel out of the box, as
part of CAMEL-163 - will try and use a single JMS transaction for
consuming and sending within the same route - the downside is due to
the spring bug (SPR-3890) we cannot reuse sessions & connections
across messages. This actually means that each message consumed will
involve the creation & closing of a new session & consumer! Which is
insanely inefficient :(

So it'd be good if folks voted for this issue...

then hopefully the spring folks will fix it :) It looks like a fairly
trivial fix too - Guillaume has even offered to provide a patch...


Open Source SOA

View raw message