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

Fixes are available

APAR status

Closed as program error.

Error description

One potential symptom of this problem is this message
logged in the SystemOut.log.
.
[10/7/10 10:00:41:008 PDT] 00000000 ContainerHelp E   WSVR0501E:
Error creating component
com.ibm.ws.websvcs.component.WASAxis2ComponentImpl@27122712
java.lang.ExceptionInInitializerError
 at java.lang.J9VMInternals.initialize(J9VMInternals.java:222)
 at
com.ibm.ws.websvcs.component.WASAxis2ComponentImpl.start(WASAxis
2ComponentImpl.java:492)
 at
com.ibm.ws.runtime.component.ContainerHelper.startComponents(Con
tainerHelper.java:538)
...
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
java.lang.ClassNotFoundException:
org.apache.commons.logging.impl.Log4JLogger
 at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFa
ctoryImpl.java:561)
 at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFa
ctoryImpl.java:272)
 at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFa
ctoryImpl.java:246)
 at
org.apache.commons.logging.LogFactory$2.run(LogFactory.java:424)
 at
java.security.AccessController.doPrivileged(AccessController.jav
a:251)
...
Caused by: org.apache.commons.logging.LogConfigurationException:
java.lang.ClassNotFoundException:
org.apache.commons.logging.impl.Log4JLogger
 at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor
(LogFactoryImpl.java:427)
 at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFa
ctoryImpl.java:554)
 ... 42 more
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:136)
 at
org.apache.commons.logging.impl.LogFactoryImpl$1.run(LogFactoryI
mpl.java:495)
.
and also this error message.
[10/7/10 10:00:41:300 PDT] 00000000 ContainerHelp E   WSVR0501E:
Error creating component
com.ibm.ws.wsaddressing.jaxws.component.WSAddressingComponentIm
java.lang.ExceptionInInitializerError
 at java.lang.J9VMInternals.initialize(J9VMInternals.java:222)
 at
com.ibm.ws.wsaddressing.jaxws.urimap.EndpointMappingListener.ini
tialize(EndpointMappingListener.java:190)
 at
com.ibm.ws.wsaddressing.jaxws.urimap.EndpointMappingListener.<in
it>(EndpointMappingListener.java:117)
 at
com.ibm.ws.wsaddressing.jaxws.component.WSAddressingComponentImp
l.start(WSAddressingComponentImpl.java:139)
 at
com.ibm.ws.runtime.component.ContainerHelper.startComponents(Con
tainerHelper.java:538)
 at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(Conta
inerImpl.java:627)
 at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.j
ava:618)
 at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(Applica
tionServerImpl.java:227)
.--------------------------------
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 PM21839 is currently targeted for inclusion in
Service Level (Fix Pack) 7.0.0.15 of 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 number
PM21839
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-02
Closed date
2010-10-27
Last modified date
2011-04-04

APAR is sysrouted FROM one or more of the following:

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

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK65060
UP11/03/04 P F103

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY UK65060

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?