[JBoss JIRA] (JBTM-1601) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1601?page=com.atlassian.jira.plugin.... ]
Michael Musgrove closed JBTM-1601.
----------------------------------
> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1601
> URL: https://issues.jboss.org/browse/JBTM-1601
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3, 5.0.0.M2
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Fix For: 4.17.0
>
>
> I'm hitting an issue on qa tests for windows machines. I'm currently testing EAP 6.1.0.ER3.
> Testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 is failing when it's run on windows machines. It does not matter which JDK is used. It fails on 4.17 branch and master as well.
> This happens for jacorb.
> The fails consistently occur on 5 tests from the testcase - that are from CrashRecovery02_2_Test26 till CrashRecovery02_2_Test30.
> All of them throw assertion:
> {quote}
> junit.framework.AssertionFailedError: task client1 printed Failed.
> {quote}
> These details apply to test CrashRecovery02_2_Test27:
> The client implementation is org.jboss.jbossts.qa.CrashRecovery02.Client02a and the fail comes from line 114 (branch 4.17).
> {code}
> correct = correct && (resourceTrace1 == ResourceTrace.ResourceTraceCommit);
> {code}
> Where the value of resourceTrace1 is {{ResourceTraceNone}}.
> I didn't get with investigation further so far.
> Steps for reproducing could be handy (using narayana.sh script first):
> 1. export NARAYANA_BUILD=0
> export NARAYANA_TESTS=0
> export CP_NARAYANA_AS=0
> export AS_BUILD=0
> export XTS_AS_TESTS=0
> export TXF_TESTS=0
> export XTS_TESTS=0
> export txbridge=0
> export QA_TESTS=1
> export SUN_ORB=0
> export QA_TARGET=test
> export QA_PROFILE="-Dtest=crashrecovery02_2"
> export WORKSPACE=$PWD
> 2. run naryana.sh - there was problem with paths for me so the command looks like this at the end
> {quote}
> sh scripts/hudson/narayana.sh -Demma.jar.location=c:\\tmp\\ochaloup\\ext -Demma.enabled=false -Dorson.jar.location=\\tmp\\ochaloup\\ext
> {quote}
> You can check whole stacktrace from job on jenkins:
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> Do you think that you could check this?
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-1601) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1601?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1601:
-----------------------------------
Fix Version/s: 4.17.0
> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1601
> URL: https://issues.jboss.org/browse/JBTM-1601
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3, 5.0.0.M2
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Fix For: 4.17.0
>
>
> I'm hitting an issue on qa tests for windows machines. I'm currently testing EAP 6.1.0.ER3.
> Testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 is failing when it's run on windows machines. It does not matter which JDK is used. It fails on 4.17 branch and master as well.
> This happens for jacorb.
> The fails consistently occur on 5 tests from the testcase - that are from CrashRecovery02_2_Test26 till CrashRecovery02_2_Test30.
> All of them throw assertion:
> {quote}
> junit.framework.AssertionFailedError: task client1 printed Failed.
> {quote}
> These details apply to test CrashRecovery02_2_Test27:
> The client implementation is org.jboss.jbossts.qa.CrashRecovery02.Client02a and the fail comes from line 114 (branch 4.17).
> {code}
> correct = correct && (resourceTrace1 == ResourceTrace.ResourceTraceCommit);
> {code}
> Where the value of resourceTrace1 is {{ResourceTraceNone}}.
> I didn't get with investigation further so far.
> Steps for reproducing could be handy (using narayana.sh script first):
> 1. export NARAYANA_BUILD=0
> export NARAYANA_TESTS=0
> export CP_NARAYANA_AS=0
> export AS_BUILD=0
> export XTS_AS_TESTS=0
> export TXF_TESTS=0
> export XTS_TESTS=0
> export txbridge=0
> export QA_TESTS=1
> export SUN_ORB=0
> export QA_TARGET=test
> export QA_PROFILE="-Dtest=crashrecovery02_2"
> export WORKSPACE=$PWD
> 2. run naryana.sh - there was problem with paths for me so the command looks like this at the end
> {quote}
> sh scripts/hudson/narayana.sh -Demma.jar.location=c:\\tmp\\ochaloup\\ext -Demma.enabled=false -Dorson.jar.location=\\tmp\\ochaloup\\ext
> {quote}
> You can check whole stacktrace from job on jenkins:
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> Do you think that you could check this?
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-1770) Fix up pretty-printing of success/failures in build
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1770?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1770:
-----------------------------------
Fix Version/s: 4.17.5
> Fix up pretty-printing of success/failures in build
> ---------------------------------------------------
>
> Key: JBTM-1770
> URL: https://issues.jboss.org/browse/JBTM-1770
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 5.0.0.M4
> Reporter: Mark Little
> Assignee: Michael Musgrove
> Priority: Trivial
> Fix For: 4.17.5
>
>
> TS jtax .......................... SUCCESS [1:02.017s]
> [INFO] Narayana: ArjuntaJTS narayana-jts-jacorb .......... SUCCESS [7.963s]
> [INFO] Narayana: ArjunaJTS integration ................... SUCCESS [33.609s]
> [INFO] Narayana: rest-tx ................................. SUCCESS [0.009s]
> [INFO] Narayana: rest-tx util ............................ SUCCESS [2.646s]
> [INFO] Narayana: rest-tx tx (RESTful API for Atomic Transactions) SUCCESS [34.522s]
> [INFO] Narayana: rest-tx webservice ...................... SUCCESS [0.720s]
> [INFO] Narayana: rest-tx integration ..................... SUCCESS [4.862s]
> [INFO] Narayana: txbridge ................................ SUCCESS [3.460s]
> [INFO] Narayana: fileio .................................. SUCCESS [1.089s]
> [INFO] Narayana: STM ..................................... SUCCESS [29.172s]
> [INFO] Narayana: txframework ............................. SUCCESS [2.526s]
> [INFO] Narayana: narayana-full ........................... SUCCESS [13.753s]
> Maybe remove the (RESTful API for Atomic Transactions) text, or shorten it.
--
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
10 years, 8 months
[JBoss JIRA] (JBTM-1770) Fix up pretty-printing of success/failures in build
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1770?page=com.atlassian.jira.plugin.... ]
Michael Musgrove closed JBTM-1770.
----------------------------------
> Fix up pretty-printing of success/failures in build
> ---------------------------------------------------
>
> Key: JBTM-1770
> URL: https://issues.jboss.org/browse/JBTM-1770
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 5.0.0.M4
> Reporter: Mark Little
> Assignee: Michael Musgrove
> Priority: Trivial
> Fix For: 4.17.5
>
>
> TS jtax .......................... SUCCESS [1:02.017s]
> [INFO] Narayana: ArjuntaJTS narayana-jts-jacorb .......... SUCCESS [7.963s]
> [INFO] Narayana: ArjunaJTS integration ................... SUCCESS [33.609s]
> [INFO] Narayana: rest-tx ................................. SUCCESS [0.009s]
> [INFO] Narayana: rest-tx util ............................ SUCCESS [2.646s]
> [INFO] Narayana: rest-tx tx (RESTful API for Atomic Transactions) SUCCESS [34.522s]
> [INFO] Narayana: rest-tx webservice ...................... SUCCESS [0.720s]
> [INFO] Narayana: rest-tx integration ..................... SUCCESS [4.862s]
> [INFO] Narayana: txbridge ................................ SUCCESS [3.460s]
> [INFO] Narayana: fileio .................................. SUCCESS [1.089s]
> [INFO] Narayana: STM ..................................... SUCCESS [29.172s]
> [INFO] Narayana: txframework ............................. SUCCESS [2.526s]
> [INFO] Narayana: narayana-full ........................... SUCCESS [13.753s]
> Maybe remove the (RESTful API for Atomic Transactions) text, or shorten it.
--
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
10 years, 8 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 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
10 years, 8 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 commented on JBTM-1249:
-------------------------------------
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
10 years, 8 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 resolved JBTM-1249.
---------------------------------
Resolution: 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
10 years, 8 months
[JBoss JIRA] (JBTM-1982) Use logger to log all the exception stacktraces instead of several Exception.printStackTrace() calls which uses the stdout
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created JBTM-1982:
--------------------------------------
Summary: Use logger to log all the exception stacktraces instead of several Exception.printStackTrace() calls which uses the stdout
Key: JBTM-1982
URL: https://issues.jboss.org/browse/JBTM-1982
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JTA, JTS
Affects Versions: 4.17.10
Reporter: Ondřej Chaloupka
Assignee: Tom Jenkinson
Priority: Minor
The arjuna code uses pattern e.printStackTrace() on several places in the code. This would be better to be changed for a logger would be used.
For ArjunaJTA I counted 28 (excluding tests) places where the logger is not used and I suppose it should be.
Secondary. It would be nice in case of the XAException the error code would be printed together with the exception stacktrace. I have one example where I would appreciated it for example.
It's ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java
method handleOrphan where after the xares.rollback(xid) is called the exception is printed to stdout + log does not contain the error code.
This issue was moved from https://bugzilla.redhat.com/show_bug.cgi?id=1007384.
--
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
10 years, 8 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:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 6.0.0.Final)
> 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
10 years, 8 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 reassigned JBTM-1249:
-----------------------------------
Assignee: Tom Jenkinson (was: Gytis Trikleris)
> 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: 6.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
10 years, 8 months