[ http://issues.apache.org/jira/browse/JDO-438?page=all ]

Michelle Caisse updated JDO-438:
--------------------------------

    Attachment: RefreshAllSideEffects.java

I've attached a new file RefreshAllSideEffects.java that replaces both 
RefreshAllWithArraySideEffects.java and 
RefreshAllWithCollectionSideEffects.java. The new test invokes refreshAll() 
with both a Collection and Object[] parameter sequentially depending on the 
value of a flag:

            if (useCollection)
                pm1.refreshAll(points1);
            else pm1.refreshAll(points1.toArray());

Michael, it would be great if you could test this on a multicore machine. To 
test, you will need to modify conf/pm.conf or create a simple test conf file 
referencing the new file name.

Please review.  It's a bit ugly.


> More Derby "ERROR 40XL1" issues with multithreaded tests
> --------------------------------------------------------
>
>                 Key: JDO-438
>                 URL: http://issues.apache.org/jira/browse/JDO-438
>             Project: JDO
>          Issue Type: Bug
>          Components: tck20
>    Affects Versions: JDO 2 final
>            Reporter: Michael Bouschen
>         Assigned To: Michelle Caisse
>             Fix For: JDO 2 maintenance release 1
>
>         Attachments: derby-dsid-pm-junit.txt, RefreshAllSideEffects.java
>
>
> I see the same DERBY error: "ERROR 40XL1: A lock could not be obtained within 
> the time requested" as reported in JDO-324 for two different test cases: 
> - RefreshAllWithArraySideEffects 
> - RefreshAllWithCollectionSideEffects
> The reason might be that I switched to a dual core machine.
> JDO-324 fixed test  case RefreshAllNoParameterSideEffects. Maybe we need to 
> apply the same fix to the other test cases RefreshAllWithArraySideEffects and 
> RefreshAllWithCollectionSideEffects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to