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

[Tom Jenkinson (JIRA)]

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

Tom Jenkinson edited comment on JBTM-1249 at 10/14/13 10:49 AM:
----------------------------------------------------------------

As the proposed fix is to change documentation to state that you shouldn't change a value from a default to something that won't work I am going to mark this as out of date.

To the reported, please note that the configuration option to change would actually be in IronJacamar or WildFly, not JBTM. In my opinion, the question would be along the lines of "How do I configure Oracle 10g in WildFly".
                
      was (Author: tomjenkinson):
    As the proposed fix is to change documentation to ensure someone doesn't change the value from a default to something that won't work I am going to mark this as out of date.
                  
> Update documentation to resolve 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, Documentation, 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
>             Fix For: 5.0.0.Final
>
>         Attachments: TestEJB.zip
>
>   Original Estimate: 20 minutes
>  Remaining Estimate: 20 minutes
>
> 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