[jbossts-issues] [JBoss JIRA] (JBTM-1138) crashrecovery12 tests intermittently fail when running in ExecutionWrapper mode
Ivo Studensky (JIRA)
jira-events at lists.jboss.org
Tue Apr 24 06:44:17 EDT 2012
[ https://issues.jboss.org/browse/JBTM-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687041#comment-12687041 ]
Ivo Studensky commented on JBTM-1138:
-------------------------------------
And need to say that I verified it by the presence of hornetq object store subdirectory in /qa directory. So it looks that it really works as expected.
> crashrecovery12 tests intermittently fail when running in ExecutionWrapper mode
> -------------------------------------------------------------------------------
>
> Key: JBTM-1138
> URL: https://issues.jboss.org/browse/JBTM-1138
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.16.3
> Reporter: Ivo Studensky
> Assignee: Tom Jenkinson
> Fix For: 4.16.4
>
> Attachments: crashrecovery12.patch
>
>
> The crashrecovery12 tests intermittently fail when running on HornetQ journal based object store, i.e. in ExecutionWrapper mode.
> Without any patch Test03 and Test06 fail. With my patch, see attached file, the tests fail intermittently, i.e. once they fail on Test02 [1], once on Test04 [2] or on Test03 [3]. The Test06 seems to be fixed with my patch.
> I did the patch according to instructions by Jonathan, but apparently I missed something.
> Jonathan's instruction:
> {quote}
> The tests are wrong.
> When in ExecutionWrapper mode, each spawned task gets its own store
> unless it's explicitly told to reuse an earlier one. Most crash rec
> tests that need to 'share' a store between consecutive processes for
> before/after crash state have a final param to createTask that gives the
> shared name, see e.g. TestGroup_crashrecovery02_01. That's missing in
> the failing tests. Change the tests to add the same string as a final
> param to the createTask calls and to ensure the client task is
> terminated before the outcome task starts. It should be anyhow as it
> commits suicide, but the framework does not necessarily know that and
> may get unhappy if it think you're trying to make concurrent processes
> use the same store.
> Jonathan.
> {quote}
> [1] https://hudson.qa.jboss.com/hudson/view/JBoss%20TS/view/JBossTS-EAP6-CI/job/jbossts-test-4.16.x-hqobjectstore/12/
> [2] https://hudson.qa.jboss.com/hudson/view/JBoss%20TS/view/JBossTS-EAP6-CI/job/jbossts-test-4.16.x-hqobjectstore/11/
> [3] https://hudson.qa.jboss.com/hudson/view/JBoss%20TS/view/JBossTS-EAP6-CI/job/jbossts-test-4.16.x-hqobjectstore/8/
--
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
More information about the jbossts-issues
mailing list