[JBoss JIRA] (JBTM-1249) Update documentation to resolve XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1249:
--------------------------------
Parent: (was: JBTM-1184)
Issue Type: Bug (was: Sub-task)
> 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: Gytis Trikleris
> Labels: jboss, jts, recovery, xa
> Fix For: 5.0.0.Final
>
> 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
13 years, 1 month
[JBoss JIRA] (JBTM-861) Enhance XTS AS7 configuration
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-861?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson commented on JBTM-861:
------------------------------------
Should this be moved to the AS7 Jira instance or does it require changes to JBTM?
> Enhance XTS AS7 configuration
> -----------------------------
>
> Key: JBTM-861
> URL: https://issues.jboss.org/browse/JBTM-861
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: XTS
> Affects Versions: 4.15.2
> Reporter: Andrew Dinn
> Priority: Minor
>
> The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported.
> XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations.
> The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service.
--
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
13 years, 1 month
[JBoss JIRA] (JBTM-1490) Track JBossWS 4.2.0.Alpha1
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1490:
-----------------------------------
Summary: Track JBossWS 4.2.0.Alpha1
Key: JBTM-1490
URL: https://issues.jboss.org/browse/JBTM-1490
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
Waiting for Alessio to release JBossWS 4.2.0.Alpha1 and have the component upgrade merged into AS master.
--
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
13 years, 1 month