Submitter complaining that 100's of threads are blocked in the following code. This is hampering performance.

"Thread-78624" #79207 daemon prio=5 os_prio=64 tid=0x0000000109eed800 nid=0x135f1 waiting for monitor entry [0xfffffffe914fe000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:404)
        - waiting to lock <0x00000004cbb1eac0> (a weblogic.utils.classloaders.ChangeAwareClassLoader)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:186)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:50)
        at com.sun.org.apache.xerces.internal.utils.ObjectFactory.findProviderClass(ObjectFactory.java:209)
        at com.sun.org.apache.xerces.internal.utils.ObjectFactory.newInstance(ObjectFactory.java:157)
        at com.sun.org.apache.xerces.internal.utils.ObjectFactory.newInstance(ObjectFactory.java:143)
        at com.sun.org.apache.xerces.internal.impl.dv.DTDDVFactory.getInstance(DTDDVFactory.java:64)
        at com.sun.org.apache.xerces.internal.impl.dv.DTDDVFactory.getInstance(DTDDVFactory.java:49)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.<init>(XML11Configuration.java:578)

Even though the contention is seen in the weblogic classload code, the provider classloading code could be improved