[jbossts-issues] [JBoss JIRA] (JBTM-1234) WSTX test MultiCloseTest failure
Paul Robinson (JIRA)
jira-events at lists.jboss.org
Tue Sep 4 03:42:32 EDT 2012
[ https://issues.jboss.org/browse/JBTM-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715527#comment-12715527 ]
Paul Robinson commented on JBTM-1234:
You can do the following check to see if an issue is actually similar to JBTM-1202:
The code for the participant completion Close tests will look something like this:
bpm1 = bam.enlistForBusinessAgreementWithParticipantCompletion(p, "1240");
bpm2 = bam.enlistForBusinessAgreementWithParticipantCompletion(fp, "5679");
//Some exception handling code which I have omitted here.
Essentially, what is happening is that you register one or more participants for participant completion. Then you notify the coordinator that each participant has completed. This is an async call which can be overtaken by the call to uba.close(). To simulate the case where the uba.close() overtakes, you can simply comment out one of the calls to bpm.complete().
In this particular case, one participant fails to close, so I'd recommend running this test twice. once with the first call to 'completed' commented out and the second test with the second call to 'completed' commented out. It should be clear by comparing the output to the hudson output if you really have got a JBTM-1202.
You should also be able to enable logging for the bit of code in XTS that checks that all participant completion participants have completed, when the client calls 'close'. Andrew and I had a look for this code, but we ran out of time. I'll have a look fort this if I get chance as it should make spotting issues like this easier in the future.
> WSTX test MultiCloseTest failure
> Key: JBTM-1234
> URL: https://issues.jboss.org/browse/JBTM-1234
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Affects Versions: 5.0.0.M1
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 4.17.0, 5.0.0.M2
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
More information about the jbossts-issues