You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (JIRA)" <ji...@apache.org> on 2010/08/13 21:24:15 UTC
[jira] Resolved: (OPENJPA-1753)
TestMixedLockManagerLockPermutation: Timing issue determines the
pass/no-pass of the test case
[ https://issues.apache.org/jira/browse/OPENJPA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee resolved OPENJPA-1753.
---------------------------------
Fix Version/s: 2.0.1
Resolution: Fixed
> TestMixedLockManagerLockPermutation: Timing issue determines the pass/no-pass of the test case
> ----------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1753
> URL: https://issues.apache.org/jira/browse/OPENJPA-1753
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Fay Wang
> Assignee: Albert Lee
> Priority: Minor
> Fix For: 2.0.1, 2.1.0
>
> Attachments: trace_fail.txt, trace_success.txt
>
>
> This test case spawns three threads and the pass/no pass of the test cases depends on the timing.
> One example is TestMixedLockManagerFindPermutation.testFindReadPessimisticRead:
> commonFindTest(
> "testFind(Read,Commit/PessimisticRead,Rollback)",
> LockModeType.READ, Act.CommitTx, 1, null,
> LockModeType.PESSIMISTIC_READ, Act.RollbackTx, 1, null);
> If the find by the second child [Thread-8] is executed before the jdbc commit of the update statement by the first child [Thread-7], the test will fail. Attached are the trace file for the successful run and failing run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.