tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomcat Random <tomcat.ran...@gmail.com>
Subject Re: Logging makes a grown man cry
Date Wed, 04 Dec 2013 15:57:13 GMT
That seems like a good solution. Are you able to avoid having a single
giant catalina.out file in $CATALINA_HOME/logs?


On Tue, Dec 3, 2013 at 11:01 PM, Dale Ogilvie <Dale_Ogilvie@trimble.com>wrote:

> Currently we use tomcat configured as out-of-the-box for logging (no
> log4j) and log4j.jar and config in the app war file.
>
> We found issues with trying to have log4j in catalina/lib.
>
> That said, it would be nice to use log4j for tomcat, however we found
> that the two configurations collided in our slf4j setup.
>
> Dale
>
> -----Original Message-----
> From: Tomcat Random [mailto:tomcat.random@gmail.com]
> Sent: Wednesday, 4 December 2013 7:12 a.m.
> To: Tomcat Users List
> Subject: Logging makes a grown man cry
>
> So, all I want is to have:
>
> 1. one log file that rolls daily (a new file each day), with the date
> appended, that catches my own logging code in the app, based on a global
> logging level value that I can change (DEBUG, or INFO, or ERROR etc) as
> needed.
>
> 2. Another log file that rolls daily and consolidates any other output
> of the server and app (or two separate files) and also has a logging
> level value that can be changed globally.
>
> 3. Get rid of the empty localhost. file.
>
> MTIA,
> Alec
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message