| Summary: | Potential infinite loop in SDODataFactoryDelegate in some ClassLoader architectures | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Blaise Doughan <blaise.doughan> | ||||
| Component: | Eclipselink | Assignee: | Blaise Doughan <blaise.doughan> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipselink.sdo-inbox | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 175786 [details]
SDO - Fix
Now check to see if the parent class loader is null or the same as the current class loader. Fixed checked into 2.1.1 at rev: 7964 Fixed checked into trunk at rev: 7965 Code reviewed by David McCann The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
The following code in SDODataFactoryDelegate can cause an infinte loop in cases where aClassLoader == aClassLoader.getParent(). // check the hierarchy to see if the interface loader is a parent of the context loader while (null != parentLoader && !loadersAreRelated) { if (parentLoader == interfaceLoader) { loadersAreRelated = true; } parentLoader = contextLoader.getParent(); }