[jbossts-issues] [JBoss JIRA] Commented: (JBTM-752) JBoss TM can not recover the failed XA resource if two XA resource join the transaction but only one XA resource fail to commit

[Jonathan Halliday (JIRA)]

    [ https://jira.jboss.org/browse/JBTM-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12536042#action_12536042 ] 

Jonathan Halliday commented on JBTM-752:
----------------------------------------

likely a dupl of JBTM-377.

> JBoss TM can not recover the failed XA resource if two XA resource join the transaction but only one XA resource fail to commit
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-752
>                 URL: https://jira.jboss.org/browse/JBTM-752
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Recovery
>    Affects Versions: 4.2.3.SP8, 4.2.3.CP07
>         Environment: JBOSS TS 4.2.3-SP8 + JBOSS AS 4.2.2 community
>            Reporter: yong deng
>            Priority: Critical
>
>     I have a J2EE application. It starts a transacition and involve two XA resource. One is JBoss messaging while the other is Oracle database.
>     I set a debug breakpoint in the XAResource.commit API of the two XA resources.
>     During the transaction commit phase, I only let one XA resource commit and before the other XA resource commit, I kill the JBOSS application server.
>     After JBoss restart, I can see following warning log continually poll out. Transaction manager has two transaction branches record in the state but only one transaction branch fails to commit. The failed branch can never get to be recovered any more.
>     I think this should be a regression, as the same case can work for JBoss TS 4.2.3 - SP6.
> 2010-06-11 19:49:48,869 WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 26, 24, 1-a6f0342:f9d:4c11f185:17ca6f0342:f9d:4c11f185:17f                                                                               >
> 2010-06-11 19:49:48,869 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.gandiva.inventory.StaticInventory_1] -  cannot find null implementation.
> 2010-06-11 19:49:48,869 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_21] - BasicAction.restore_state - could not recover 175047490
> 2010-06-11 19:49:48,869 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtomicAction: transaction not activated, unable to replay phase 2 commit

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