| Summary: | LockOnCloneDeadlockAvoidanceTest failed on JDK 1.7 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Edwin Tang <edwin.tang> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | david.minsky | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Edwin Tang
The regression is related to David Minsky's check-in(for bug 331164) on revision 9403. Discussed with Gordon: LockOnCloneDeadlockAvoidanceTest fails on JDK1.7, but not on JDK1.6 as the JDK1.7 TreeMap throws an NPE when put(Object, Object) is invoked with null, (ConcurrentPerson instance) respectively. Upon further inspection, the cached 'person' attribute in LockOnCloneDeadlockAvoidanceTest has a null primary key, and the JDK1.7 failure is exposing this testing problem. To resolve this, we should instead cache the object returned from the uow registration call. Created attachment 197137 [details]
Proposed fix
Fixed in 2.3 revision: 9495 The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |