Once again you are the man. The solution was probably somewhere in the 
archives, if so I apologise as I'm having a lazy day and it's easier to ask. 
I'm actually getting something now and just need to tweak the properties file 
to get what I want.

Thanks again

-----Original Message-----
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 09 December 2004 16:03
To: Tomcat Users List
Subject: RE: Tomcat 5.5 Webapp logging.



Hi,
Also need commons-logging.jar (not commons-logging-api.jar) in
common/lib for this to work.  The docs have already been patched in CVS.

Yoav Shapira http://www.yoavshapira.com
 

>-----Original Message-----
>From: Dale, Matt [mailto:[EMAIL PROTECTED]
>Sent: Thursday, December 09, 2004 11:00 AM
>To: Tomcat Users List
>Subject: RE: Tomcat 5.5 Webapp logging.
>
>Hi,
>
>I can't even get it to create the log file and see no log4j related
>messages in the catalina.out. Below is my log4j.properties which is in
>common/classes
>
>log4j.rootLogger=debug, R
>log4j.appender.R=org.apache.log4j.RollingFileAppender
>log4j.appender.R.File=/usr/local/jakarta/tomcat-5.5.4/logs/tomcat.log
>log4j.appender.R.MaxFileSize=100MB
>log4j.appender.R.MaxBackupIndex=10
>log4j.appender.R.layout=org.apache.log4j.PatternLayout
>log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
>log4j.logger.org.apache.catalina=DEBUG, R
>
>I have put log4j-1.2.9.jar in common lib.
>
>I would have thought that at least the file would be created even if
>nothing was in it.
>
>Any ideas?
>
>Ta
>Matt
>
>-----Original Message-----
>From: Dale, Matt
>Sent: 09 December 2004 15:41
>To: Tomcat Users List
>Subject: RE: Tomcat 5.5 Webapp logging.
>
>
>
>That's the one I tried but never got too far. I'll give it a another
whirl
>and it should cut down on the errors from the 3rd party app in the
short
>term and as long as they aren't in catalina.out i'll be happy.
>
>Ta
>Matt
>
>
>-----Original Message-----
>From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
>Sent: 09 December 2004 15:18
>To: Tomcat Users List
>Subject: RE: Tomcat 5.5 Webapp logging.
>
>
>
>Hi,
>The example in
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html
>is a decent start.  Since your goal is to reduce messages being output
to
>the log, at least for this 3rd party application, add a line like
>log4j.logger.rootPackageOf3rdPartyApp = WARN
>to the sample file at the above URL, and you should be all set.
>
>Yoav Shapira http://www.yoavshapira.com
>
>-----Original Message-----
>From: Dale, Matt [mailto:[EMAIL PROTECTED]
>Sent: Thursday, December 09, 2004 10:14 AM
>To: Tomcat Users List (E-mail)
>Subject: Tomcat 5.5 Webapp logging.
>
>Hi,
>We have a 3rd party application which has a nasty habit of chucking out
a
>load of messages to stdout and stderr.
>Up until tomcat 5 we used a console Logger with swallowOutput turned on
to
>catch all that output so it didnt end up in catalina.out.
>Obviously in 5.5 this is not possible and Log4J seems to be the way to
go.
>I've tried this but not having much luck. I think it's just that I
don't
>understand the log4j.properties file.
>Could someone perhaps post a sample that would do roughly what I need
and I
>can tweak it from there.
>Ta
>Matt
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary and/or privileged.  This e-mail is intended only for the
>individual(s) to whom it is addressed, and may not be saved, copied,
>printed, disclosed or used by anyone else.  If you are not the(an)
intended
>recipient, please immediately delete this e-mail from your computer
system
>and notify the sender.  Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business 
communication, and may contain information that is confidential, proprietary 
and/or privileged.  This e-mail is intended only for the individual(s) to whom 
it is addressed, and may not be saved, copied, printed, disclosed or used by 
anyone else.  If you are not the(an) intended recipient, please immediately 
delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not 
the intended recipient or the person responsible for delivering to the intended 
recipient, be advised that you have received this E-mail in error and that any 
use or copying is strictly prohibited. If you have received this E-mail in 
error please notify the beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual 
sender and not beCogent Ltd. You must take full responsibility for virus 
checking this email and any attachments.
Please note that the content of this email or any of its attachments may 
contain data that falls within the scope of the Data Protection Acts and that 
you must ensure that any handling or processing of such data by you is fully 
compliant with the terms and provisions of the Data Protection Act 1984 and 
1998.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to