activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattias Jiderhamn (JIRA)" <>
Subject [jira] [Commented] (AMQ-3059) Provide support for suspend/resume of transactions
Date Tue, 20 Nov 2012 11:22:59 GMT


Mattias Jiderhamn commented on AMQ-3059:

I've set up a test case to demonstrate the problem here:

The behaviour seems to differ a bit depending on the application server / JTA implementation,
so I've included two different test cases for Atomikos and Bitronix.

Resin - which we are using - seems to behave like the Bitronix test case. According to my
investigations, the problem in that case is caused by the fact that org.apache.activemq.TransactionContext.start()
sets the synchronizations to null, which means the sync added in org.apache.activemq.ActiveMQMessageConsumer.registerSync()
is forgotten. The effect seems to be that even though the tx is rolled back, the message is
still ack:ed as having been received.

While digging I came across commit 1034430 (
referring to AMQ-3022. Previous to that commit, a tx resume would cause an exception, which
from my perspective would have been much better, so that the lack of support for suspend/resume
would have been easily detected rather being silently ignored with the effect that messages
dissappear. I therefore suggest at least reverting 1034430 until proper suspend/resume has
been implemented.
> Provide support for suspend/resume of transactions 
> ---------------------------------------------------
>                 Key: AMQ-3059
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.3.1, 5.3.2, 5.4.0, 5.4.1
>            Reporter: Andrei Stefan
> Suspend/resume of transactions is not supported in ActiveMQ at the moment (
There are situations where this feature is useful and has a valid usage:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message