[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:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
(was: 4.17.4)
> 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: Sub-task
> 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, 2 months
[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:
--------------------------------
Summary: Update documentation to resolve XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule) (was: XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule))
> 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: Sub-task
> 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: 4.17.4, 5.0.0.M2
>
> 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, 2 months
[JBoss JIRA] (JBTM-1249) 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:
--------------------------------
Assignee: Gytis Trikleris (was: Tom Jenkinson)
> 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: Sub-task
> 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: 4.17.4, 5.0.0.M2
>
> 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, 2 months
[JBoss JIRA] (JBTM-1422) Deployment failure because of missing service dependencies
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1422?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1422:
-------------------------------------
Looks like an Arquillian issue. Lets see if it happens again. I don't think we can talk to the Arq team about this until it's reproducible.
> Deployment failure because of missing service dependencies
> ----------------------------------------------------------
>
> Key: JBTM-1422
> URL: https://issues.jboss.org/browse/JBTM-1422
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M2
>
>
> See: http://172.17.131.2/job/narayana/141
> {noformat}
> org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase Time elapsed: 16103 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsba-participant-completion.war
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
> ...
> Caused by: java.lang.Exception: {
> "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsba-participant-completion.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"],
> "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"wsba-participant-completion.war\".FIRST_MODULE_USE"],
> "Services that may be the cause:" => [
> "jboss.module.spec.service.\"deployment.arquillian-service\".main",
> "jboss.txn.TransactionSynchronizationRegistry",
> "jboss.txn.UserTransactionRegistry"
> ]
> }
> }
> ...
> {noformat}
> {noformat}
> org.jboss.as.test.xts.simple.wsat.client.WSATTestCase Time elapsed: 1846 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsat.war
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
> ...
> Caused by: java.lang.Exception: {
> "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsat.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"],
> "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"wsat.war\".FIRST_MODULE_USE"],
> "Services that may be the cause:" => [
> "jboss.module.spec.service.\"deployment.arquillian-service\".main",
> "jboss.txn.TransactionSynchronizationRegistry",
> "jboss.txn.UserTransactionRegistry"
> ]
> }
> }
> ...
> {noformat}
--
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, 2 months
[JBoss JIRA] (JBTM-1422) Deployment failure because of missing service dependencies
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1422?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1422:
--------------------------------
Priority: Trivial (was: Minor)
> Deployment failure because of missing service dependencies
> ----------------------------------------------------------
>
> Key: JBTM-1422
> URL: https://issues.jboss.org/browse/JBTM-1422
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Gytis Trikleris
> Assignee: Paul Robinson
> Priority: Trivial
> Fix For: 5.0.0.M2
>
>
> See: http://172.17.131.2/job/narayana/141
> {noformat}
> org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase Time elapsed: 16103 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsba-participant-completion.war
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
> ...
> Caused by: java.lang.Exception: {
> "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsba-participant-completion.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"],
> "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"wsba-participant-completion.war\".FIRST_MODULE_USE"],
> "Services that may be the cause:" => [
> "jboss.module.spec.service.\"deployment.arquillian-service\".main",
> "jboss.txn.TransactionSynchronizationRegistry",
> "jboss.txn.UserTransactionRegistry"
> ]
> }
> }
> ...
> {noformat}
> {noformat}
> org.jboss.as.test.xts.simple.wsat.client.WSATTestCase Time elapsed: 1846 sec <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: wsat.war
> at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:83)
> ...
> Caused by: java.lang.Exception: {
> "JBAS014771: Services with missing/unavailable dependencies" => ["jboss.module.service.\"deployment.wsat.war\".main is missing [jboss.module.spec.service.\"deployment.arquillian-service\".main]"],
> "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"wsat.war\".FIRST_MODULE_USE"],
> "Services that may be the cause:" => [
> "jboss.module.spec.service.\"deployment.arquillian-service\".main",
> "jboss.txn.TransactionSynchronizationRegistry",
> "jboss.txn.UserTransactionRegistry"
> ]
> }
> }
> ...
> {noformat}
--
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, 2 months
[JBoss JIRA] (JBTM-1249) 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:
--------------------------------
Fix Version/s: 5.0.0.M2
(was: 5.0.0.Final)
> 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: Sub-task
> 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: 4.17.4, 5.0.0.M2
>
> 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, 2 months
[JBoss JIRA] (JBTM-1278) Additional debug information required for transaction's Xid with Oracle
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1278?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1278:
--------------------------------
Fix Version/s: (was: 4.6.1.CP14)
(was: 4.17.4)
I am going to make this change on master, we can back port it should the need arise
> Additional debug information required for transaction's Xid with Oracle
> -----------------------------------------------------------------------
>
> Key: JBTM-1278
> URL: https://issues.jboss.org/browse/JBTM-1278
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Affects Versions: 4.16.1
> Environment: Jboss EAP 5.x
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> It seems that Oracle is returning different XIDs each time (with the same content) which makes it difficult to debug if the same XID is in more than one scan. Additional debug information is required in Xid to make debugging easier.
--
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, 2 months