Fixes are available
APAR status
Closed as program error.
Error description
EJBDeploy may fail with the following error: Caused by: rg.apache.commons.logging.LogConfigurationException: Class org.apache.commons.logging.impl.Jdk 14Logger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor (LogFactoryImpl.java:416) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFa ctoryImpl.java:525) ... 76 more 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.getLogConstructor (LogFactoryImpl.java:412) ... 77 more
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM WebSphere Application * * Server EJBDeploy tool. * **************************************************************** * PROBLEM DESCRIPTION: EJBDeploy fails to generate the * * deployment code if the application * * contains common-logging code and makes * * use of custom mappings. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem was caused by limitation places on classloader by commons logging described in http://wiki.apache.org/commons/Logging/FrequentlyAskedQuestions In the EJBDeploy scenario multiple classloaders are loading the LogFactory: [LogFactory from java.net.URLClassLoader@1905488275] [ENV] Class org.apache.commons.logging.LogFactory was loaded via classloader java.net.URLClassLoader@1905488275 [LogFactory from java.net.URLClassLoader@1905488275] [ENV] Ancestry of classloader which loaded org.apache.commons.logging.LogFactory is java.net.URLClassLoader@1905488275 == 'java.net.URLClassLoader@71937193' [LogFactory from java.net.URLClassLoader@1905488275] [ENV] Ancestry of classloader which loaded org.apache.commons.logging.LogFactory is ClassLoader tree:java.net.URLClassLoader@1905488275 --? org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@1446729 --? org.eclipse.osgi.baseadaptor.BaseAdaptor$ParentClassLoader@16565 --? BOOT
Problem conclusion
The limitation can be worked around by restoring the context cla ssloader of the EJBDeploy thread after all the EJBDeploy code ge neration but before RMIC is called upon the generated code. That way the commons-logging library and custom converter can be used . The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.21. 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
PM43711
Reported component name
RATL APP DEV WI
Reported component ID
5724J1901
Reported release
755
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-14
Closed date
2011-08-30
Last modified date
2011-08-30
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
RATL APP DEV WI
Fixed component ID
5724J1901
Applicable component levels
R755 PSY
UP
R754 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
30 August 2011