Fixes are available
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
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.47: WebSphere Application Server V6.1 Fix Pack 47
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: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
If the application is packaged with org.apache.commons.logging classes or if the application defines is own custom LogFactory, the application may not start. An error similar to the following may occur: java.lang.ExceptionInInitializerError at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet(Servl etWrapper.java:1896) ... Caused by: java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.initialize(J9VMInternals.java:222) at java.lang.J9VMInternals.initialize(J9VMInternals.java:167) ... Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4jFactory at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:609) The error indicates that the Log4jFactory cannot be found, even if the application contains a Log4jFactory.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Feature * * Pack for Web Services users of JAX-WS * **************************************************************** * PROBLEM DESCRIPTION: The JAX-WS application may fail to * * start if the application is packaged * * with org.apache.commons.logging * * classes. * **************************************************************** * RECOMMENDATION: Install a fixpack containing this APAR and * * APAR PM09917. * **************************************************************** If the application is packaged with org.apache.commons.logging classes, or if the application defines its own custom LogFactory, the application may not start. An error similar to the following may occur: java.lang.ExceptionInInitializerError at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet(Servl etWrapper.java:1896) ... Caused by: java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.initialize(J9VMInternals.java:222) at java.lang.J9VMInternals.initialize(J9VMInternals.java:167) ... Caused by: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4jFactory at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:609) The error indicates that the Log4jFactory cannot be found, even if the application contains a Log4jFactory.
Problem conclusion
The JAX-WS runtime is changed to defer the LogFactory initialization code until after the application starts. If similar errors occur when the application is run, please install a fixpack containing PM09877. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.33. 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 number
PM07020
Reported component name
WEBSERVIC FEATU
Reported component ID
5724J0850
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-08
Closed date
2010-03-23
Last modified date
2010-03-23
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
WEBSERVIC FEATU
Fixed component ID
5724J0850
Applicable component levels
R610 PSY
UP
Document Information
Modified date:
24 October 2021