Re: Redirecting stderr to RotatingFileHandler

I have seen a Java file that provides that functionality somewhere in the documentation, website, code. I don't remember where I saw it so you may ahve to dig a bit. On Apr 11, 2005 5:30 PM, Neil Benn <[EMAIL PROTECTED]> wrote: > Hello, > > Sorry for asking such a basic question but I

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

AW: Multiple loggers, same application?

Tested and confirmed, thanks Curt! This was exactly what I was looking for (and a single prop file is fine). -D > -Original Message- > From: Curt Arnold [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 12, 2005 11:39 AM > To: Log4J Users List > Subject: Re: Multiple loggers, same appl

RE: Multiple loggers, same application?

Hi Bender, Three different Loggers, each with their own Appenders as configured (preferably) through separate property files. Utilize standard appenders as configured. I'll rename 'ErrorLogger' to 'CodeLogger' to avoid confusion. i.e. AuditLogger configured through securitylog.properties --append

Re: Multiple loggers, same application?

You may need to tweak this for your own requirements. Almost all of the log4j examples demonstrate using classnames for logger names, however this is a case where you would want to use a slightly different pattern. Hopefully, you have read http://logging.apache.org/log4j/docs/manual.html and

RE: Multiple loggers, same application?

Darren you must make more clear what you want to achieve: Do you want only three different destinations (appenders) to log to? Or do you want three different loggers, each one with his own set of appenders? What is the kind of the desired appenders? How do you want to distinguish the different lo

RE: Log4j failed to initialize in Jbuilder 2005 web run/debug

Hi Jacob, thanks for the reply. I tried your suggestion but the problem persisted. Like you (and James, thanks for your comment btw) I reckoned that there was a problem with Tomcat as it obviously wasn't starting up, however I had the cause down to Log4j because that was where it was sticking and

Multiple loggers, same application?

Hey all, Having a real hard time finding any information regarding my problem. I have an application, and within each class I would like to configure three separate Loggers, each having their own severitys: SecurityLogger ErrorLogger AuditLogger But, I would like each of these loggers to have

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

RE: Date in French

Hello, Thanks for your answer, i will try your trick. In any case, your explanation i useful ! Antoine -Message d'origine- De : Curt Arnold [mailto:[EMAIL PROTECTED] Envoyé : vendredi 8 avril 2005 16:49 A : Log4J Users List Objet : Re: Date in French I assume that your default locale

isDebugEnabled()

Hi all, following is the typical call stack when calling log4j's isDebugEnabled: +-> log.isDebugEnabled() +-> repository.isDisabled() +-> this.getEffectiveLevel() +-> level.isGreaterOrEqual() Seems pretty heavy load for me (when debugging disabled). This is only because repository.isDis