Summary: | Some testSetup failed within jpa.advanced on server with "name is already used by an existing object" exception | ||
---|---|---|---|
Product: | z_Archived | Reporter: | Kevin Yuan <kevin.yuan> |
Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | Keywords: | test |
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Kevin Yuan
2009-02-11 16:19:16 EST
This is new regression since the following checkin by Chris: SVN Checkin: Bug 241765 - JPA 2.0 Derived identities https://bugs.eclipse.org/bugs/show_bug.cgi?id=241765 reviewed by Gordon and Guy Several JPA test suites use the same table creator and call "new AdvancedTableCreator().replaceTables(JUnitTestCase.getServerSession());" in each of them, and it failed intermittently on running all of them together. Need to dig into it. It could be something to do with failing tests on the server not cleaning up resources, since the testSetup tests that fail seem to follow closely other tests that fail. After OptimisticLock issue fix (the bug 264582), this issue also has been fixed. Mass update to change fixed in target. Mass update to change fixed in target. Mass update to change fixed in target. Mass update to change fixed in target. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |