Hello
 
As we are not providing any log4j configuration for individual web app, I 
guess, Tomcat is directing all the log4j log messages in the code to system.out 
which in turn is being written to catalina.out
 
Agree that it may not be a good idea to direct log messages from all web apps 
to a same log file. But, our requirement is that there should be a single file.
Considering all these, is there a way to achieve rolling for catalina.out, 
based on size ?
 
Thanks

--- On Mon, 1/12/09, Caldarale, Charles R <chuck.caldar...@unisys.com> wrote:

From: Caldarale, Charles R <chuck.caldar...@unisys.com>
Subject: RE: Logging configuration in Tomcat
To: "Tomcat Users List" <users@tomcat.apache.org>
Date: Monday, January 12, 2009, 6:41 PM

> From: Jay [mailto:difficult...@yahoo.com]
> Subject: RE: Logging configuration in Tomcat
>
> There are many web apps. Log4j logger is used in all web apps
> & there are no system.out  or system.err

Then where is your catalina.out usage coming from?  Tomcat does not itself put
anything in catalina.out; data in there appears only because the Tomcat startup
script redirects System.out and System.err to that file.

> If I configure log4j at each web app level using
> log4j.properties, am abile to achive log file rotation but,
> this requires one log file per web application.

Which really, really is what you need.  Lumping them all together will create
serious grief, as other posters have already pointed out.

> What I am interested is one log file for all web apps

A bad idea.  You could just merge the log files after they've been
generated.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




      

Reply via email to