-
Bug
-
Resolution: Fixed
-
P3
-
5.0u8
-
1.4
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2153487 | 7 | Joe Wang | P3 | Closed | Fixed | b15 |
JDK-2144026 | 6u2 | Santiago Pericasgeertsen | P3 | Resolved | Fixed | b01 |
JAXP contains a number of calls to dprint, which are never printed unless the jaxp.debug flag is set.
A number of the strings created to call dprint are quite expensive to calculate. For the appserver, it is *very* expensive to calculate toString from the classloader, which contains many, many jar files. So in particular, the dPrint calls that use the classloader:
dPrint("found jar resource=" + serviceId + " using ClassLoader: " + cl);
dPrint("created new instance of " + providerClass + " using ClassLoader: " + cl)
have a significant impact on our performance.
All these calls should create strings only if the debug flag is set, rather than always creating the strings.
A number of the strings created to call dprint are quite expensive to calculate. For the appserver, it is *very* expensive to calculate toString from the classloader, which contains many, many jar files. So in particular, the dPrint calls that use the classloader:
dPrint("found jar resource=" + serviceId + " using ClassLoader: " + cl);
dPrint("created new instance of " + providerClass + " using ClassLoader: " + cl)
have a significant impact on our performance.
All these calls should create strings only if the debug flag is set, rather than always creating the strings.
- backported by
-
JDK-2144026 JAXP debug messages unnecessarily calculate expensive strings
-
- Resolved
-
-
JDK-2153487 JAXP debug messages unnecessarily calculate expensive strings
-
- Closed
-