PK84750: WEB SERVICES LOGFACTORY ISN'T BEING IMPORTED PROPERLY

Fixes are available

APAR status

Closed as program error.

Error description

When a JAX-WS application is called, the following exception
may occur in the logs:

Caused by:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Jdk14Logger does not implement
Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFa
ctoryImpl.java:532)
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.getLog(LogFactory.java:395
)
at
com.ibm.ws.webservices.utils.DetachableInputStream.<clinit>(Deta
chableInputStream.java:66)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS web services                      *
*                                                              *
****************************************************************
* PROBLEM DESCRIPTION: When a JAX-WS application is called,    *
*                      a LogConfigurationException error may   *
*                      occur.                                  *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
When a JAX-WS application is called, the following exception
may occur in the logs if you include your own version of
org.apache.commons.logging in your application.

Caused by:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Jdk14Logger does not implement
Log
 at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFa
ctoryImpl.java:532)
 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.getLog(LogFactory.java:395
)
 at
com.ibm.ws.webservices.utils.DetachableInputStream.<clinit>(Deta
chableInputStream.java:66)
 at java.lang.J9VMInternals.initializeImpl(Native Method)
 at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
 ... 27 more

Problem conclusion

Web Services runtime is incorrectly importing the Apache
LogFactory. The incorrect classes have been fixed to use a
different mechanism to log messages.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK84750
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-15
Closed date
2009-05-07
Last modified date
2009-05-07

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

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

Document Information

Modified date:
24 October 2021

Tips

PK84750: WEB SERVICES LOGFACTORY ISN'T BEING IMPORTED PROPERLY

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

Document Information

Share your feedback

Need support?