camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: JMS and transaction
Date Sat, 28 Jan 2012 09:18:11 GMT
Spring Transaction does not support using multiple threads. The
transactional work should be done in the same thread, from spring TX
manager point of view.

On Fri, Jan 27, 2012 at 5:29 PM, Hervé BARRAULT
<herve.barrault@gmail.com> wrote:
> Hi,
>
> I found in archive that parallel processing is not compatible with transaction.
>
> Is it still relevant or is there a workaround ?
>
> Regards
>
> Hervé
>
> On 1/27/12, Hervé BARRAULT <herve.barrault@gmail.com> wrote:
>> Hi,
>>
>> I have two question about a route, JMS and transactions.
>>
>> The use is : one request response Web service put message on n queues
>> (using transaction ensure the message really put in all queues or no
>> one).
>>
>> Does this route make sense (only "pseudo" route not all the stuff to
>> manage transaction i guess) ?
>>
>> from("cxf:bean:myEndpoint").
>> .wireTap("direct:tap")
>> .process(myProcessor)
>> transacted("PROPAGATION_REQUIRES_NEW")
>> .multicast()
>> .parallelProcessing()
>> .recipientList(header("MY_HEADER"))
>> .end()
>> .process(myAnswerProcessor);
>>
>> from(direct:tap).process(myOptionalProcessor);
>>
>> If it could work, when is the transaction commit ?
>>
>> Thanks for answers.
>>
>> Regards
>> Hervé
>>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message