[jbossts-issues] [JBoss JIRA] (JBTM-1249) XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule)

Michel PRUNET (JIRA) jira-events at lists.jboss.org
Wed Sep 26 09:57:04 EDT 2012

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

Michel PRUNET commented on JBTM-1249:

A simple workaround is to set pad-xid to false.
Oracle 11g doesn't need it anymore. 


> XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule)
> ----------------------------------------------------------------------------------
>                 Key: JBTM-1249
>                 URL: https://issues.jboss.org/browse/JBTM-1249
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Application Server Integration, JCA, JTS
>    Affects Versions: 4.16.2
>         Environment: JBoss AS 7.1.1 Final, Windows, Oracle
>            Reporter: Michel PRUNET
>            Assignee: Tom Jenkinson
>              Labels: jboss, jts, recovery, xa
>         Attachments: TestEJB.zip
> The XARecoveryManager is unable to recover an Oracle Prepared Transaction. 
> The reason: 
> Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource). 
> When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is not padded (retrieved from the tx-object-store).  The XID contained in the RecoveryXids are padded (retrieved from oracle). When the method execute xids.remove(xid), it never found the xid. The transaction is never recovered.
> In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or bqual_length), the transaction will be recovered successfully.

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: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list