activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Broken transaction when using async send
Date Mon, 07 Apr 2014 15:27:49 GMT
please add your 2c to that jira and maybe vote for it to show your interest.

On 7 April 2014 15:51, ld4711 <ext-lars.ditzel@here.com> wrote:
> That sounds good! We are looking forward for the implementation. Meanwhile we
> will be using sync mode.
>
> We would also appreciate a warning hint on the documentation pages that
> default asynchronous send mode might show that behavior under special
> circumstances. Users should be aware of that risk.
>
> Thanks,
> Lars
>
>
> gtully wrote
>> there is a related discussion here:
>> https://issues.apache.org/jira/browse/AMQ-3166
>>
>> my thinking is that a failure to send async should mark  the
>> transaction rollbackOnly so that the commit will always fail in that
>> event.
>> So you send async in the hope that all is well and the transaction
>> boundary gives you feedback.
>>
>> If you need more immediate feedback they a sync Send is needed.
>> alwaysSyncSend option on the CF
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Broken-transaction-when-using-async-send-tp4680119p4680122.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
http://redhat.com
http://blog.garytully.com

Mime
View raw message