PK55978: EXCEPTIONININITIALIZERERROR CAUSED BY CLASSNOTFOUNDEXCEPTION USING WSIF-2.0 API WITH WEBSPHERE APPLICATION SERVER

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• A java.lang.ExceptionInInitializerError (caused by
  ClassNotFoundException) occurs when using WSIF-2.0 API with
  WebSphere.
  
  Details of the error as found in the trace.log are as follows:
  
  java.lang.ExceptionInInitializerError
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:205)
   at
  org.apache.wsif.providers.soap.apacheaxis.WSIFDynamicProvider_Ap
  acheAxis
  .setUpBindingNamespaceURIs(Unknown Source)
   at
  org.apache.wsif.providers.soap.apacheaxis.WSIFDynamicProvider_Ap
  acheAxis
  .<clinit>(Unknown Source)
   .
   .
  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:131)
   at
  org.apache.commons.logging.impl.LogFactoryImpl$1.run(LogFactoryI
  mpl.java
  :466)
   at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:193)
   at
  org.apache.commons.logging.impl.LogFactoryImpl.loadClass(LogFact
  oryImpl.
  java:454)
   at
  org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor
  (LogFact
  oryImpl.java:406
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM WebSphere Application Server    *
  *                 Applications that invoke the Web Services    *
  *                 Invocation Framework WSIF-2.0 Application    *
  *                 Programming Interface (API)                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: A java.lang.ExceptionInInitializerError *
  *                      (caused by a ClassNotFoundException)    *
  *                      occurs when using the WSIF-2.0 API      *
  *                      from within a WebSphere application.    *
  ****************************************************************
  * RECOMMENDATION: Users of WebSphere Applications that         *
  *                 invoke the WSIF-2.0 API should apply this    *
  *                 fix.                                         *
  ****************************************************************
  A java.lang.ExceptionInInitializerError (caused by a
  ClassNotFoundException) occurs when using the WSIF-2.0 API
  from within a WebSphere application.
  
  This problem occurs because an unhandled ClassNotFoundException
  occurs during tracing when wsif.jar, commons-logging-1.1.jar
  and other jar files on which these depend are packaged
  with the application.
  
  Details of the error as found in the trace.log are as follows:
  
  java.lang.ExceptionInInitializerError
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:205)
   at org.apache.wsif.providers.soap.apacheaxis.
     WSIFDynamicProvider_ApacheAxis.setUpBindingNamespaceURIs
     (Unknown Source)
   at org.apache.wsif.providers.soap.apacheaxis.
     WSIFDynamicProvider_ApacheAxis.<clinit> (Unknown Source)
   .
   .
  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:131)
   at org.apache.commons.logging.impl.LogFactoryImpl$1.run
     (LogFactoryImpl.java:466)
   at java.security.AccessController.doPrivileged
     (AccessController.java:193)
   at org.apache.commons.logging.impl.LogFactoryImpl.loadClass
    (LogFactoryImpl.java:454)
   at org.apache.commons.logging.impl.LogFactoryImpl.
     getLogConstructor (LogFactoryImpl.java:406)
  

Problem conclusion

• The problem was fixed by catching and (intentionally)
  suppressing the exception that caused the problem.
  
  This fix is targeted for inclusion in 6.1.0.15: WebSphere
  Application Server V6.1.0 Fix Pack 15
  Please refer to the recommended updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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:

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP