activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Rodos (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2717) Crashing and restarting the broker causes message redelivery even if the XA transaction was already prepared (but not commited)
Date Fri, 21 May 2010 16:19:55 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eugene Rodos updated AMQ-2717:
------------------------------

    Attachment: XATransactionRecoveryTest.java

Attaching junit test that illustrates the problem.

Note that if you uncomment xaRes.commit(), the message will not be redelivered and the test
will succeed as expected.  However, if the xaRes is only prepared but not committed, the message
is redelivered.

> Crashing and restarting the broker causes message redelivery even if the XA transaction
was already prepared (but not commited)
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2717
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2717
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.1
>            Reporter: Eugene Rodos
>         Attachments: XATransactionRecoveryTest.java
>
>
> The scenario is as follows:
> \- message is delivered within an XA global transaction
> \- the XA tx completes the prepare phase
> \- the server crashes before the XA tx completes the commit
> \- the server is restarted
> \- (if the J2EE server supports XA recovery, it will recover the XA tx and complete the
commit (tested and confirmed with Websphere))
> \- ActiveMQ redelivers the message
> The redelivery should not happen.  Unless, following recovery, the TransactionManager
decides to rollback the tx, the tx will be committed.  If it is committed, the message would
have been processed already.  Redelivering it causes the message to be processed again and
breaks JMS' deliver-once-and-only-once guarantee.
> If the tx has been prepared, AMQ should not redeliver the message following a crash recovery,
 If the tx is ultimately rolled back and the message is put back on the queue, it can redeliver
it, otherwise, it should not.
> This is very difficult to write a Junit test for but I will try to come up with something...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message