strange problem

Hi, We are using log4j-1.2.17.jar and facing a strange issue. When we change log level for few packages, it takes effect correctly. For some packages, though the log level is set to INFO, their logs get printed in DEBUG all the time. We didn’t setup root logger in our config. However, even when

Re: Strange problem

At 08:25 PM 4/12/2005, Frank W. Zammetti wrote: I didn't update all copies... I didn't realize I had to as I thought the version local to the webapp would be all that matters (is this by any chance the much-discussed autodiscovery/classloader issue rearing its ugly head??) If I am not mistaken, by

Re: Strange problem

I didn't update all copies... I didn't realize I had to as I thought the version local to the webapp would be all that matters (is this by any chance the much-discussed autodiscovery/classloader issue rearing its ugly head??) I also did not update commons-logging-api.jar as I don't have that insta

Re: Strange problem

Frnak, Did you make sure to upgrade *all* copies of commons-logging.jar to 1.0.4? I believe Websphere has its own copy of JCL. Did you make sure also to upgrade commons-logging-api.jar? At 07:49 PM 4/12/2005, Frank W. Zammetti wrote: Further info... I updated JCL to 1.0.4 and removed the org.apa

Re: Strange problem

Further info... I updated JCL to 1.0.4 and removed the org.apache.commons.logging.LogFactory file... logging broke again. I put the file back, restarted the app, and logging was once again working. Log4J version is 1.2.8 incidentally, so I was almost up to date with that as well (have NOT update

Re: Strange problem

Hi Ceki, I am using an older version, but not *that* old... 1.0.3 Would you expect that upgrading from 1.0.3 to 1.0.4 (the latest production release I can see) and also removing the org.apache.commons.logging.LogFactory file would result in my logging still working as it does now with that file?

Re: Strange problem

Frank, What you suggest sounds quite wrong to me. In particular, org.apache.commons.logging.impl.Log4jFactory is deprecated [1] and should not be used. The fact that setting org.apache.commons.logging.LogFactory gives positive results indicates that you may be using an old version of JCL as Jam

Re: Strange problem

Thanks James, that did put me on the right track... just for the sake of having an answer in the archives, what solved the problem for me is adding the following file... org.apache.commons.logging.LogFactory ...(yes, that is the full filename!), with the contents... org.apache.commons.logging.im

Re: Strange problem

That sounds similar to a problem that I had recently. Search the archives for messages with a subject of "JCL+Tomcat+Log4j related problems". Basically I was having problems because my JCL jars were too old. On Apr 12, 2005 9:03 AM, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm

Strange problem

Hi all, I'm having an odd little problem here... I have a webapp where I use Log4J underneath JCL. I use an XML config file and Log4J is initialized in a ServletContextListener. The code in the listener does some hackery on the XML... basically, I construct a real path to my log files on the fl

FW: log4j strange problem

> Hi All, > > I am using log4j and creating the logs files per websphere application. > > My custom log class having the argument for category instance name and create the > respective appender file name and writing the log informations. > > Also this log class in one jar file and all instance