[JBoss JIRA] (JBTM-1287) @DataManagement injection point is null on service invocation
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1287:
-----------------------------------
Summary: @DataManagement injection point is null on service invocation
Key: JBTM-1287
URL: https://issues.jboss.org/browse/JBTM-1287
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: TXFramework
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
This causes ATTest to fail.
The problems seems to be that ServiceRequestSoapHandler#getInstance returns a different instance to that which is invoked by the service.
This used to work, but an upgrade in CXF seems to have changed the behavior.
--
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 Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1206:
-----------------------------------
Summary: 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: XTS
Reporter: Tom Jenkinson
Assignee: Amos Feng
Fix For: 5.0.0.M2
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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBTM-1289) XTS participant completion tests should use a rendezvous to delay close until participant has completed
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1289:
-----------------------------------
Summary: XTS participant completion tests should use a rendezvous to delay close until participant has completed
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 4.17.1, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord) is asynchronous. This can be overtaken by the client's "close" message, resulting in the coordinator cancelling the activity, due to not all participants being completed.
The hack is to add a delay before the client calls 'close'. We have that on the tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous. Alternatively there may be some XTS feature that we can use to poll the coordinator. Or maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present. However, we do occasionally see this issue on the XTS AS integration testsuite, which increases the priority.
--
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