[JBoss JIRA] (JBTM-1385) ATS integration SimpleIsolatedServers.testSimultaneousRecover assertion error 5
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1385?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1385:
-------------------------------------
OK, it looks like:
1. Server1 starts recovery on proxy xa resource
2. Server2 collects the list of xids from TestXAResources
3. server1 completes recovery on proxy xa resource thereby cleaning up all reference to the transaction and rollback of the TestXAResource xids in server2
4. Server2 then realises the the TestXAResources and orphan so tries to roll them back, this is fine even if they were meant to be committed they would have by now, all you get is a spurious error.
> ATS integration SimpleIsolatedServers.testSimultaneousRecover assertion error 5
> -------------------------------------------------------------------------------
>
> Key: JBTM-1385
> URL: https://issues.jboss.org/browse/JBTM-1385
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Gytis Trikleris
> Assignee: Tom Jenkinson
> Priority: Critical
> Fix For: 4.17.4, 5.0.0.M2
>
>
> See: http://172.17.131.2/job/jbossts-branch417-EAP61-java6/1525
> Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 37.972 sec <<< FAILURE!
> testSimultaneousRecover(com.arjuna.ats.jta.distributed.SimpleIsolatedServers) Time elapsed: 3.358 sec <<< FAILURE!
> java.lang.AssertionError: 5
--
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
12 years
[JBoss JIRA] (JBTM-1398) Review TXFramework's subsystem usage (and change if required)
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1398:
-----------------------------------
Summary: Review TXFramework's subsystem usage (and change if required)
Key: JBTM-1398
URL: https://issues.jboss.org/browse/JBTM-1398
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: TXFramework
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
We need to review the various options for including TXFramework subsytem code in AS7.
1. Create a new Subsytem
2. Leave it in the XTS one
Also do we want all the subsytem code to live in the narayana codebase, rather than the AS7 one?
Pros: don't need to rebuild AS7 when changing it. Don't need to raise a pull req on AS7 when we want to change it.
Cons: We have to maintain it. In the past AS7 developers have made changes as the internals of AS7 change. We don't want to have to do this ourselves.
I suggest we look at how other projects are doing this before committing to a particular method.
--
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
12 years
[JBoss JIRA] (JBTM-1145) TXFramework Code Tidy Part 2
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1145?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1145:
--------------------------------
Issue Type: Task (was: Enhancement)
> TXFramework Code Tidy Part 2
> ----------------------------
>
> Key: JBTM-1145
> URL: https://issues.jboss.org/browse/JBTM-1145
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Test restructuring
> Try using annotations in subsystem
> Remove annotations and properties that are not used.
> Remove System.out and System.err. For example:
> {code}
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,561 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleInboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.getHeaders()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.handleOutboundMessage()
> 15:08:58,562 INFO [stdout] (http-localhost-127.0.0.1-8080-1) ServiceRequestSoapHandler.close()
> {code}
> Add logging
> Refactor WSBA Handlers into one (Wrap the registration and completion into an object that switches based on participant type)
> @Required to something that matched EJB TX annotation
--
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
12 years
[JBoss JIRA] (JBTM-1206) Intermittent XTS CR bug
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1206?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1206:
--------------------------------
Fix Version/s: 4.17.4
(was: 4.17.0)
> Intermittent XTS CR bug
> -----------------------
>
> Key: JBTM-1206
> URL: https://issues.jboss.org/browse/JBTM-1206
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Tom Jenkinson
> Assignee: Paul Robinson
> Fix For: 4.17.4
>
>
> http://172.17.131.2/job/narayana-java7-idlj/51/
> [INFO] Surefire report directory: /home/hudson/workspace/narayana-java7-idlj/XTS/localjunit/crash-recovery-tests/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.arjuna.qa.junit.TestATCrashDuringCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.769 sec
> Running com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 66.163 sec
> Running com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 369.915 sec
> Running com.arjuna.qa.junit.TestATParticipantCrashAndRecover
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 0 sec
> Running com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 149.636 sec
> Running com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 74.689 sec
> Running com.arjuna.qa.junit.TestBACrashDuringCommit
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,436.51 sec
> Running com.arjuna.qa.junit.TestBACrashDuringOnePhaseCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 159.511 sec
> Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.848 sec
> Running com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 327.038 sec
> Running com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 795.378 sec <<< FAILURE!
> Results :
> Tests in error:
> subordinateMultiParticipantParticipantCompletionParticipantCloseTest(com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete): jboss-as not killed and shutdown
> Tests run: 26, Failures: 0, Errors: 1, Skipped: 3
--
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
12 years