You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by James Green <ja...@gmail.com> on 2014/09/22 13:59:32 UTC
Is this route possible..?
We want to consume from JMS and route the message through a set of
Processors which may or may not invoke database calls via DAOs.
Thing is, we want the database calls to be wrapped in a transaction, but we
don't have an XA transaction manager so the JMS part ought to be excluded.
Is this possible?
Thanks,
James
Re: Is this route possible..?
Posted by Matt Sicker <bo...@gmail.com>.
You're probably better off with a transaction manager like Geronimo's just
to coordinate all the different transaction types. Then you can use the
transacted route definitions.
On 22 September 2014 07:05, Siano, Stephan <st...@sap.com> wrote:
> Yes, it should be possible to define a transaction manager for the data
> source and make the route transacted with that one. However in that case
> the database accesses may be committed before the JMS read is committed (so
> if the removal of the message from the JMS queue fails, the database calls
> will be committed anyway.
>
> -----Original Message-----
> From: James Green [mailto:james.mk.green@gmail.com]
> Sent: Montag, 22. September 2014 14:00
> To: users
> Subject: Is this route possible..?
>
> We want to consume from JMS and route the message through a set of
> Processors which may or may not invoke database calls via DAOs.
>
> Thing is, we want the database calls to be wrapped in a transaction, but we
> don't have an XA transaction manager so the JMS part ought to be excluded.
>
> Is this possible?
>
> Thanks,
>
> James
>
--
Matt Sicker <bo...@gmail.com>
RE: Is this route possible..?
Posted by "Siano, Stephan" <st...@sap.com>.
Yes, it should be possible to define a transaction manager for the data source and make the route transacted with that one. However in that case the database accesses may be committed before the JMS read is committed (so if the removal of the message from the JMS queue fails, the database calls will be committed anyway.
-----Original Message-----
From: James Green [mailto:james.mk.green@gmail.com]
Sent: Montag, 22. September 2014 14:00
To: users
Subject: Is this route possible..?
We want to consume from JMS and route the message through a set of
Processors which may or may not invoke database calls via DAOs.
Thing is, we want the database calls to be wrapped in a transaction, but we
don't have an XA transaction manager so the JMS part ought to be excluded.
Is this possible?
Thanks,
James