commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From simon <skitch...@apache.org>
Subject Re: [Logging] Log4jLogger does not implement Log error in Websphere 6.1.0.15 environment
Date Sun, 04 May 2008 18:09:28 GMT

On Fri, 2008-04-25 at 11:23 -0500, Nitin Aurora wrote:
> 
> 
> Hi, I can't seem to start my application when using Commons-logging-1.1.jar. I am running
the application in Websphere 6.1.0.15 environment in RAD 7. The application (ear) class loader
mode is PARENT_LAST with Application as the WAS classloader mode. It seems like the commons-logging
 jar and properties file in my application is getting loaded but then the server tries to
bind the Logfactory from the application classloader to the Log interface in the Websphere
runtime jar (com.ibm.ws.runtime_6.1.0.jar) and I believe thats what triggers the following
error --  """[4/25/08 10:22:35:437 CDT] 0000000a SystemErr R Caused by: org.apache.commons.logging.LogConfigurationException:
Class org.apache.commons.logging.impl.Log4JLogger does not implement Log  at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:412)
 at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)  at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)  at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
 at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)  at com.ibm.ws.webservices.custom.CustomPropertyProviderImpl.(CustomPropertyProviderImpl.java:45)
 at com.ibm.ws.webservices.custom.CustomPropertyProviderFactory.(CustomPropertyProviderFactory.java:29)
 at java.lang.J9VMInternals.initializeImpl(Native Method)  at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
 at com.ibm.ws.webservices.tools.resource.DefaultToolEnv.(DefaultToolEnv.java:70)  at java.lang.J9VMInternals.initializeImpl(Native
Method)  at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)  at com.ibm.ws.webservices.tools.WSDLQuery.(WSDLQuery.java:119)
 at com.ibm.ws.webservices.tools.WSDLQuery.(WSDLQuery.java:103)  at com.ibm.ws.webservices.engine.deployment.wsdd.WSDDGen.getWSDLQuery(WSDDGen.java:178)
 at com.ibm.ws.webservices.engine.deployment.wsdd.WSDDPort.expand(WSDDPort.java:531)  at com.ibm.ws.webservices.engine.deployment.wsdd.WSDDPort._initTMR(WSDDPort.java:308)
 at com.ibm.ws.webservices.component.WSServerImpl.setupWsddPort(WSServerImpl.java:1126)  at
com.ibm.ws.webservices.component.WSServerImpl.warMetaDataCreated(WSServerImpl.java:1904) 
at com.ibm.ws.webservices.component.WSServerImpl.metaDataCreated(WSServerImpl.java:530)  at
com.ibm.ws.runtime.component.MetaDataMgrImpl.fireMetaDataCreated(MetaDataMgrImpl.java:188)
 at com.ibm.ws.webcontainer.metadata.WebMetaDataFactory.createMetaData(WebMetaDataFactory.java:205)
 at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaDataFromFactories(MetaDataMgrImpl.java:172)
 at com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:306)
 at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:563)  at
com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817)
 at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)
 at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2122)
 at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473) """    I dont understand why
the log interface in the runtime jar is being used to bind the Log4jLogger...(if that is the
case)...  Thanks, Nitin    _________________________________________________________________Spell
a grand slam in this game where word skill meets World Series. Get in the game.http://club.live.com/word_slugger.aspx?icid=word_slugger_wlhm_admod_april08

Although you say that you are using commons-logging-1.1, I'm not sure
that this is actually the case. That version of commons-logging should
never report "Log4Logger does not implement Log". I suspect that
somewhere in a shared libs directory of your websphere installation is
an older version of commons-logging. If you update this to 1.1 or later
(1.1.1 is the current version) then this issue will probably go away.

If not, then try enabling the "diagnostics" feature of commons-logging.
See the "troubleshooting" page of the commons-logging site:
  http://commons.apache.org/logging/troubleshooting.html

Regards,
Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org


Mime
View raw message