IV00009: DEADLOCKS OCCUR WHEN PARSING BUSINESS OBJECTS

APAR status

• Closed as program error.

Error description

• Error Message: Customer observed deadlock while parsing business
  objects during heavy load.
  .
  Stack Trace: Deadlock Threads:-
  "WebContainer : 23"
  
  ================================================================
  ========
   at
  
  com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundCla
  ssLoader
  .java:439)
  
   - locked <0x98da2b10> (a
  com.ibm.ws.classloader.CompoundClassLoader)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
  
  ================================================================
  ========
  
  
  "WebContainer : 6"
  
  ================================================================
  ========
   at
  
  com.sun.org.apache.xerces.internal.impl.dv.DTDDVFactory.getInsta
  nce(DTDD
  VFactory.java:98)
  
   - locked <0x884a62f8> (a java.lang.Class)
  
   at
  
  com.sun.org.apache.xerces.internal.impl.dv.DTDDVFactory.getInsta
  nce(DTDD
  VFactory.java:83)
  
   - locked <0x884a62f8> (a java.lang.Class)
  
   at
  
  com.sun.org.apache.xerces.internal.parsers.XML11Configuration.<i
  nit>(XML
  11Configuration.java:565)
  
  ================================================================
  ========
  .
  

Local fix

Problem summary

• For applications which excessively create new parser instances
  this eliminates contention for a lock on the class object which
  under high load may cause threads to deadlock.
  

Problem conclusion

• This defect will be fixed in:
  5.0.0 SR12 FP5
  6.0.0 SR9 FP2
  .
  JVM has been modified to address the deadlock.
  .
  To obtain the fix:
  Install build 20110520 or later
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  IV06366

Fix information

• Fixed component name

  JAVA 5 XML/XSL

• Fixed component ID

  620500126

Applicable component levels

• R500 PSY

     UP