Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6478375

JAXP debug messages unnecessarily calculate expensive strings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 1.4.0
    • 5.0u8
    • xml
    • 1.4
    • generic
    • generic
    • Verified

        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.

              spericas Santiago Pericasgeertsen
              soaks Scott Oaks (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: