[
https://issues.jboss.org/browse/JBTM-1132?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1132:
--------------------------------
Description:
See:
http://172.17.131.2/view/XTS%20recovery/job/jbossts-branch416-xts-recover...
In the trace logs you can see:
{code}
removed transaction 0:ffffac118308:6a060f8e:4f92446a:15
rollback returned for subordinate coordinator BasicAction:
0:ffffac118308:6a060f8e:4f92446a:15 status: ActionStatus.ABORTED
aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1
aborted received for Coordinator engine D0:ffffac118308:6a060f8e:4f92446a:1c
aborted received for Coordinator engine D0:ffffac118308:6a060f8e:4f92446a:1c
{code}
Here you will notice that the transaction is removed before the last participant record is
removed. There is a bug in ATSubordinateCrashDuringPrepare.txt and
BASubordinateCrashDuringPrepare.txt that will only shutdown the VM if the transaction log
is the last to be removed.
was:
See:
http://172.17.131.2/view/XTS%20recovery/job/jbossts-branch416-xts-recover...
Not more details yet.
TestATSubordinateCrashDuringPrepare fails: jboss-as not killed and
shutdown
---------------------------------------------------------------------------
Key: JBTM-1132
URL:
https://issues.jboss.org/browse/JBTM-1132
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.16.3
Reporter: Paul Robinson
Assignee: Tom Jenkinson
Fix For: 4.16.4, 5.0.0.M2
See:
http://172.17.131.2/view/XTS%20recovery/job/jbossts-branch416-xts-recover...
In the trace logs you can see:
{code}
removed transaction 0:ffffac118308:6a060f8e:4f92446a:15
rollback returned for subordinate coordinator BasicAction:
0:ffffac118308:6a060f8e:4f92446a:15 status: ActionStatus.ABORTED
aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1
aborted received for Coordinator engine D0:ffffac118308:6a060f8e:4f92446a:1c
aborted received for Coordinator engine D0:ffffac118308:6a060f8e:4f92446a:1c
{code}
Here you will notice that the transaction is removed before the last participant record
is removed. There is a bug in ATSubordinateCrashDuringPrepare.txt and
BASubordinateCrashDuringPrepare.txt that will only shutdown the VM if the transaction log
is the last to be removed.
--
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