PM21719: A ClassNotFoundException error occurs when a Log4JLogger is used with JAX-WS

APAR status

• Closed as program error.

Error description

• From checking the FFDC logs, it looks like the
  NoClassDefFoundError's  root cause is the following:
  .
  Caused by: java.lang.ClassNotFoundException:
  org.apache.commons.logging.impl.Log4JLogger
   at java.lang.Class.forNameImpl(Native Method)
   at java.lang.Class.forName(Class.java:130)
   at org.apache.commons.logging.impl.LogFactoryImpl$1.run
      (LogFactoryImpl.java:466)
   at java.security.AccessController.doPrivileged
      (AccessController.java:197)
   at org.apache.commons.logging.impl.LogFactoryImpl.
      loadClass(LogFactoryImpl.java:454)
  .
  In a osgi trace.
  1) Create a file called osgi-debug.txt somewhere on the
     filesystem
  2) Edit that file to contain the following lines (nothing else
     is necessary):
  
      org.eclipes.osgi/debug=true
      org.eclipse.osgi/debug/loader=true
  3) Add a system property to the server JVM, with the property
     name "ws.osgi.debug" and value of the location of the file.
  .
  Trace: 2010/09/01 09:41:16.540 01 t=9C02A0 c=UNK key=P8
    ThreadId: 00000012
    FunctionName: loadClass name=java.lang.ClassNotFoundException
  this=com.ibm.ws.classloader.CompoundClassLoader@64fe64fe
    SourceId: com.ibm.ws.classloader.CompoundClassLoader
    Category: FINER
    ExtendedMessage: Entry
  .
  Trace: 2010/09/01 09:41:16.541 01 t=9C02A0 c=UNK key=P8
    ThreadId: 00000012
    FunctionName: com.ibm.ws.classloader.CompoundClassLoader
    SourceId: com.ibm.ws.classloader.CompoundClassLoader
    Category: FINEST
    ExtendedMessage: loaded java.lang.ClassNotFoundException
    from parent
  Trace: 2010/09/01 09:41:16.541 01 t=9C02A0 c=UNK key=P8
    ThreadId: 00000012
    FunctionName: com.ibm.ws.classloader.CompoundClassLoader
    SourceId: com.ibm.ws.classloader.CompoundClassLoader
    Category: FINEST
    ExtendedMessage: loaded java.lang.ClassNotFoundException
    using classloader=null
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All administrators of IBM WebSphere         *
  *                  Application Server JAX-WS Web services      *
  *                  applications which include Jakarta Commons  *
  *                  Logging classes.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: The JAX-WS Web service application may  *
  *                      not start due to a                      *
  *                      ClassNotFoundException error.           *
  ****************************************************************
  * RECOMMENDATION:  Apply a fixpack that contains this APAR.    *
  ****************************************************************
  When a JAX-WS Web service application includes the Jakarta
  Commons Logging classes within their application or classpath,
  a ClassNotFoundException may occur.
  

Problem conclusion

• The problem occurs when the JAX-WS application uses
  logger classes (like Log4JLogger) that are not contained in
  the JAX-WS runtime.
  
  The JAX-WS runtime is corrected to tolerate this scenario by
  using its own logger during its own internal processing.
  
  APAR PM21719 is currently targeted for inclusion in
  Service Level (Fix Pack) 6.1.0.35 WebSphere
  Application Server.
  
  Please refer to URL:
  //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack availability.
  

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:

  PM21839

Fix information

• Fixed component name

  WEBSERVICE FEAT

• Fixed component ID

  5655I3550

Applicable component levels

• R610 PSY

     UP