Community
Participate
Working Groups
The JPA test JUnitJPQLComplexTestSuite.testPessimisticLock does not work on MaxDB. It hangs when the second EntityManager reads the locked entity. I rewrote the test so that it preserves the intention of the test (patch attached). I tested it successfully on MaxDB and MySQL. As we don't have a SAP committer any more - could any of the others commit that for me, please? (Provided the patch is okay, of course...) We would need the patch in 2.3 and trunk. Thanks and best regards, Sabine
Created attachment 210908 [details] Test JUnitJPQLComplexTestSuite.testPessimisticLock rewritten
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
Fix checked in. Tested with JPA LRG Reviewed: Tom Ware reviewed user submitted fix
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink