openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fay Wang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1753) TestMixedLockManagerLockPermutation: Timing issue determines the pass/no-pass of the test case
Date Fri, 30 Jul 2010 16:29:16 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Fay Wang updated OPENJPA-1753:
------------------------------

    Attachment: trace_fail.txt
                trace_success.txt

> 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
>            Priority: Minor
>             Fix For: 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.


Mime
View raw message