[jboss-jira] [JBoss JIRA] Closed: (JBAS-5571) When JBossMQ does XA recovery it should always write the XID to the log

Adrian Brock (JIRA) jira-events at lists.jboss.org
Fri May 30 11:36:46 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBAS-5571?page=all ]

Adrian Brock closed JBAS-5571.
------------------------------

    Resolution: Done

This has been done.

If the XARecovery is enabled and it is XA (i.e. the txid is a XID) then if prepare request completes,
we make sure there a TX record is written before returning XA_OK to the caller,
even if there are no changes to messages in the transaction.

> When JBossMQ does XA recovery it should always write the XID to the log
> -----------------------------------------------------------------------
>
>                 Key: JBAS-5571
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5571
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS (JBossMQ)
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
>
>
> There's a problem in JBossMQ when XARecovery is enabled, but all the messages are temporary.
> In this case, the lazy write of the XID to the log doesn't get invoked so the transaction manager
> doesn't know how to recover it properly after a crash.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list