Log4jLogger does not implement Log error in Websphere 6.1.0.15 environment‏ - Websphere

This is a discussion on Log4jLogger does not implement Log error in Websphere 6.1.0.15 environment‏ - Websphere ; 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. Both commons-logging-1.1.jar ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Log4jLogger does not implement Log error in Websphere 6.1.0.15 environment‏

  1. Log4jLogger does not implement Log error in Websphere 6.1.0.15 environment‏

    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. Both commons-logging-1.1.jar and log4j-1.2.8.jar are in the ear. 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.LogConfigurationExcepti on: Class org.apache.commons.logging.impl.Log4JLogger does not implement Log at org.apache.commons.logging.impl.LogFactoryImpl.get LogConstructor(LogFactoryImpl .java:412) at org.apache.commons.logging.impl.LogFactoryImpl.new Instance(LogFactoryImpl.java: 525) at org.apache.commons.logging.impl.LogFactoryImpl.get Instance(LogFactoryImpl.java: 272) at org.apache.commons.logging.impl.LogFactoryImpl.get Instance(LogFactoryImpl.java: 246) at org.apache.commons.logging.LogFactory.getLog(LogFa ctory.java:395) at com.ibm.ws.webservices.custom.CustomPropertyProvid erImpl.(CustomPropertyProvide rImpl.java:45) at com.ibm.ws.webservices.custom.CustomPropertyProvid erFactory.(CustomPropertyProv iderFactory.java:29) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.j ava:177) at com.ibm.ws.webservices.tools.resource.DefaultToolE nv.(DefaultToolEnv.java:70) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.j ava: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.WSDD Gen.getWSDLQuery(WSDDGen.java :178) at com.ibm.ws.webservices.engine.deployment.wsdd.WSDD Port.expand(WSDDPort.java:531 ) at com.ibm.ws.webservices.engine.deployment.wsdd.WSDD Port._initTMR(WSDDPort.java:3 08) at com.ibm.ws.webservices.component.WSServerImpl.setu pWsddPort(WSServerImpl.java:1 126) at com.ibm.ws.webservices.component.WSServerImpl.warM etaDataCreated(WSServerImpl.j ava:1904) at com.ibm.ws.webservices.component.WSServerImpl.meta DataCreated(WSServerImpl.java :530) at com.ibm.ws.runtime.component.MetaDataMgrImpl.fireM etaDataCreated(MetaDataMgrImp l.java:188) at com.ibm.ws.webcontainer.metadata.WebMetaDataFactor y.createMetaData(WebMetaDataF actory.java:205) at com.ibm.ws.runtime.component.MetaDataMgrImpl.creat eMetaDataFromFactories(MetaDa taMgrImpl.java:172) at com.ibm.ws.runtime.component.MetaDataMgrImpl.creat eMetaData(MetaDataMgrImpl.jav a:306) at com.ibm.ws.runtime.component.DeployedModuleImpl.st art(DeployedModuleImpl.java:5 63) at com.ibm.ws.runtime.component.DeployedApplicationIm pl.start(DeployedApplicationI mpl.java:817) at com.ibm.ws.runtime.component.ApplicationMgrImpl.st artApplication(ApplicationMgr Impl.java:949) at com.ibm.ws.runtime.component.ApplicationMgrImpl$Ap pInitializer.run(ApplicationM grImpl.java:2122) at com.ibm.wsspi.runtime.component.WsComponentImpl$_A synchInitializer.run(WsCompon entImpl.java:342) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava: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

  2. Re: Log4jLogger does not implement Log error in Websphere 6.1.0.15 environment‏

    See http://wiki.apache.org/jakarta-commo...AskedQuestions



    There's a section entitled Log4JLogger does not implement Log that will be of assistance. I found that reading the Redpaper for WAS 6.1 Classloader issues ( http://www.redbooks. ibm.com/abstracts/redp4307.html) was of great help as well. A lot of behaviour has changed in WAS 6.1.



    Good luck!

  3. Re: Log4jLogger does not implement Log error in Websphere 6.1.0.15 environment‏

    Any luck with problem? I am in the same boat, but I've 6.1.0.13 with WebServices Feature Pak.



    At first, I thought may be I should get the latest patch, since you are having the same problem with the latest patch I'm not planning to apply to it soon until I resolve this issue first.

+ Reply to Thread