Hi Jim, Just a thought - you say the application has been running without this error except for the last week or so, and then this week no problems.
It sounds to me as though a particular use case may have arisen where an incorrect logging statement is being invoked, and that this use case had not arisen previously (i.e. the problem was always in the code, but until invoked, no problems). Thats my 2p :-) Eric -----Original Message----- From: Collins, Jim [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 21. Jänner 2003 15:35 To: 'Tomcat Users List' Subject: RE: Please help with LogConfigurationException Hi Yoav, Thanks for your reply. I could see it was commons logging throwing the exception and I tried changing the actual logging implementation that it uses to log4J to see if that would stop it happening but it did not. I don't really think it is a commons logging problem either because it works and logs correctly until this exception get thrown. Last week this exception was being thrown at least twice a day however since Friday no more exceptions have been thrown. It just seems bizarre to me that it should suddenly start happening and then stop. Regards Jim. > -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED]] > Sent: 21 January 2003 14:24 > To: Tomcat Users List > Subject: RE: Please help with LogConfigurationException > > > Howdy, > A couple of things: > > - It's commons-logging, not tomcat, that's throwing the > exception. It's > most likely misconfigured, i.e. you have some jars (probably the > commons-logging jars themselves) in the wrong place. > > - Can you temporarily take out commons logging, i.e. code directly to > JDK 1.4 logging or log4j or whatever you want, and see if the problem > goes away? > > - Try to ask on the commons-logging mailing list. > > Yoav Shapira > Millennium ChemInformatics > > > >-----Original Message----- > >From: Collins, Jim [mailto:[EMAIL PROTECTED]] > >Sent: Tuesday, January 21, 2003 4:24 AM > >To: 'Tomcat Users List' > >Subject: RE: Please help with LogConfigurationException > > > >Hi, > > > >I have still had no feedback at all on this. Can anyone > please help I > am > >running out of hair to pull out. > > > >Regards > > > >Jim > > > >> -----Original Message----- > >> From: Collins, Jim [mailto:[EMAIL PROTECTED]] > >> Sent: 20 January 2003 09:47 > >> To: 'Tomcat Users List' > >> Subject: Please help with LogConfigurationException > >> > >> > >> Hi, > >> > >> I am still getting this Exception thrown. Has anyone else > >> ever had this and > >> know of a fix. Any help at all would be appreciated as this > >> is causing me a > >> lot of problems > >> > >> Thanks > >> > >> Jim. > >> > >> > A quick update. I have now copied the log4J jar file to > >> > commons/lib and > >> > restarted the server so that is now uses log4J instead of the > >> > JDK1.4 logger. > >> > After a couple of hours I got this error: > >> > > >> > org.apache.commons.logging.LogConfigurationException: > >> > org.apache.commons.logging.LogConfigurationException: > >> > org.apache.commons.logging.LogConfigurationException: Class > >> > org.apache.commons.logging.impl.Log4JCategoryLog does not > >> > implement Log > >> > at > >> > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Log > >> > FactoryImpl.ja > >> > va:530) > >> > at > >> > org.apache.commons.logging.impl.LogFactoryImpl.getInstance(Log > >> > FactoryImpl.ja > >> > va:285) > >> > at > >> > org.apache.commons.logging.LogFactory.getLog(LogFactory.java:401) > >> > at > >> > org.apache.tomcat.util.log.CommonLogHandler.log(CommonLogHandl > >> > er.java:97) > >> > at org.apache.tomcat.util.log.Log.log(Log.java:198) > >> > at org.apache.tomcat.util.log.Log.log(Log.java:192) > >> > at org.apache.tomcat.util.log.Log.log(Log.java:174) > >> > at > >> > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > >> > ThreadPool.jav > >> > a:536) > >> > at java.lang.Thread.run(Thread.java:536) > >> > Caused by: org.apache.commons.logging.LogConfigurationException: > >> > org.apache.commons.logging.LogConfigurationException: Class > >> > org.apache.commons.logging.impl.Log4JCategoryLog does not > >> > implement Log > >> > at > >> > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstruct > >> > or(LogFactoryI > >> > mpl.java:415) > >> > at > >> > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Log > >> > FactoryImpl.ja > >> > va:523) > >> > ... 8 more > >> > Caused by: > >> org.apache.commons.logging.LogConfigurationException: Class > >> > org.apache.commons.logging.impl.Log4JCategoryLog does not > >> > implement Log > >> > at > >> > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstruct > >> > or(LogFactoryI > >> > mpl.java:411) > >> > ... 9 more > >> > > >> > Could anyone please give me some clue as to what I can do. > >> I have not > >> > changed anything for some time now and prior to these errors > >> > that have just > >> > started happening I have not had to restart the server for > >> > weeks. Now I am > >> > having to start it more than once every day. > >> > > >> > Thanks > >> > > >> > Jim. > >> > > >> > > -----Original Message----- > >> > > From: Collins, Jim [mailto:[EMAIL PROTECTED]] > >> > > Sent: 17 January 2003 12:31 > >> > > To: 'Tomcat Users List' > >> > > Subject: RE: Log Error > >> > > > >> > > > >> > > I have upgraded the JDK to 1.4.1 and it is still happening. > >> > > > >> > > > -----Original Message----- > >> > > > From: Collins, Jim > >> > > > Sent: 17 January 2003 10:04 > >> > > > To: 'Tomcat Users List' > >> > > > Subject: Log Error > >> > > > > >> > > > > >> > > > Hi, > >> > > > > >> > > > I am using Tomcat4.1.10 and JDK1.4.0 and I have started to > >> > > > get the following error message after which Tomcat crashes. > >> > > > > >> > > > org.apache.commons.logging.LogConfigurationException: > >> > > > org.apache.commons.logging.LogConfigurationException: > >> > > > org.apache.commons.logging.LogConfigurationException: Class > >> > > > org.apache.commons.logging.impl.Jdk14Logger does not > >> implement Log > >> > > > at > >> > > > > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Log > >> > > > FactoryImpl.java:530) > >> > > > at > >> > > > > org.apache.commons.logging.impl.LogFactoryImpl.getInstance(Log > >> > > > FactoryImpl.java:285) > >> > > > at > >> > > > > >> org.apache.commons.logging.LogFactory.getLog(LogFactory.java:401) > >> > > > at > >> > > > > org.apache.tomcat.util.log.CommonLogHandler.log(CommonLogHandl > >> > > > er.java:97) > >> > > > at org.apache.tomcat.util.log.Log.log(Log.java:198) > >> > > > at org.apache.tomcat.util.log.Log.log(Log.java:192) > >> > > > at org.apache.tomcat.util.log.Log.log(Log.java:174) > >> > > > at > >> > > > > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > >> > > > ThreadPool.java:536) > >> > > > at java.lang.Thread.run(Thread.java:536) > >> > > > Caused by: > >> > > > org.apache.commons.logging.LogConfigurationException: > >> > > > org.apache.commons.logging.LogConfigurationException: Class > >> > > > org.apache.commons.logging.impl.Jdk14Logger does not > >> implement Log > >> > > > at > >> > > > > org.apache.commons.logging.impl.LogFactoryImpl.getLogConstruct > >> > > > or(LogFactoryImpl.java:415) > >> > > > at > >> > > > > org.apache.commons.logging.impl.LogFactoryImpl.newInstance(Log > >> > > > FactoryImpl.java:523) > >> > > > ... 8 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.getLogConstruct > >> > > > or(LogFactoryImpl.java:411) > >> > > > ... 9 more > >> > > > > >> > > > I have not changed anything to the configuration and it was > >> > > > working fine in the past I have just started to notice this > >> > > > in the last week or so. If anyone has any ideas what I can do > >> > > > to resolve this I would appreciate it. > >> > > > > >> > > > Thanks > >> > > > > >> > > > Jim. > >> > > > > >> > >> > >> PLEASE READ: The information contained in this email is > confidential > >> and intended for the named recipient(s) only. If you are not > >> an intended > >> recipient of this email you must not copy, distribute or take any > >> further action in reliance on it and you should delete it and > >> notify the > >> sender immediately. Email is not a secure method of > communication and > >> Nomura International plc cannot accept responsibility for the > accuracy > >> or completeness of this message or any attachment(s). Please > >> examine this > >> email for virus infection, for which Nomura International > plc accepts > >> no responsibility. If verification of this email is sought then > please > >> request a hard copy. Unless otherwise stated any views or opinions > >> presented are solely those of the author and do not represent those > of > >> Nomura International plc. This email is intended for informational > >> purposes only and is not a solicitation or offer to buy or sell > >> securities or related financial instruments. Nomura > >> International plc is > >> regulated by the Financial Services Authority and is a > member of the > >> London Stock Exchange. > >> > >> > >> > >> -- > >> To unsubscribe, e-mail: > >> <mailto:[EMAIL PROTECTED]> > >> For additional commands, e-mail: > >> <mailto:[EMAIL PROTECTED]> > >> > > > > > >PLEASE READ: The information contained in this email is confidential > >and intended for the named recipient(s) only. If you are not an > intended > >recipient of this email you must not copy, distribute or take any > >further action in reliance on it and you should delete it and notify > the > >sender immediately. Email is not a secure method of communication and > >Nomura International plc cannot accept responsibility for > the accuracy > >or completeness of this message or any attachment(s). Please examine > this > >email for virus infection, for which Nomura International plc accepts > >no responsibility. If verification of this email is sought > then please > >request a hard copy. Unless otherwise stated any views or opinions > >presented are solely those of the author and do not > represent those of > >Nomura International plc. This email is intended for informational > >purposes only and is not a solicitation or offer to buy or sell > >securities or related financial instruments. Nomura International plc > is > >regulated by the Financial Services Authority and is a member of the > >London Stock Exchange. > > > > > > > >-- > >To unsubscribe, e-mail: <mailto:tomcat-user- > >[EMAIL PROTECTED]> > >For additional commands, e-mail: <mailto:tomcat-user- > >[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > PLEASE READ: The information contained in this email is confidential and intended for the named recipient(s) only. If you are not an intended recipient of this email you must not copy, distribute or take any further action in reliance on it and you should delete it and notify the sender immediately. Email is not a secure method of communication and Nomura International plc cannot accept responsibility for the accuracy or completeness of this message or any attachment(s). Please examine this email for virus infection, for which Nomura International plc accepts no responsibility. If verification of this email is sought then please request a hard copy. Unless otherwise stated any views or opinions presented are solely those of the author and do not represent those of Nomura International plc. This email is intended for informational purposes only and is not a solicitation or offer to buy or sell securities or related financial instruments. Nomura International plc is regulated by the Financial Services Authority and is a member of the London Stock Exchange. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
