tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eric Miller" <>
Subject Re: Tomcat 5.5.4, Logging and the death of my friend localhost_log
Date Fri, 12 Nov 2004 18:53:18 GMT
Actually, I guess the default isn't that bad for UNIX/Linux anyway. In 
theory, if you are using J2SE 1.5 with the default log settings and you 
don't have Log4J installed, INFO level messages and above will get written 
to the console which gets redirected to catalina.out by So, 
instead of having catalina.out, plus the other log, everything instead just 
goes into catalina.out. This is fine for my purposes, I just wanted to make 
sure that I wouldn't be missing important exceptions. As far as I know, if 
an unhandled exception occurs, it will get logged to catalina.out. If that's 
the case, then I'm happy.

The only thing that I need to figure out now, is what is supposed to be 
better about Log4J over standard JDK logging and whether I actually need 
whatever that is. I'm guessing maybe log rotation or something?

The other thing that I noticed is that a JDK file seems 
to only allow you to specify a single FileHandler. I thought that it would 
let you assign different files to different loggers, but, as far as I can 
tell, this isn't possible (using the properties file anyway). Maybe this is 
one of the limitations?


----- Original Message ----- 
From: "Remy Maucherat" <>
To: "Tomcat Users List" <>
Sent: Thursday, November 11, 2004 2:02 PM
Subject: Re: Tomcat 5.5.4, Logging and the death of my friend localhost_log

> On Thu, 11 Nov 2004 15:25:48 -0000, Allistair Crossley
> <> wrote:
>> Now, I know Logger has been removed from 5.5 series and that we are 
>> supposed to be using some kind of log4j / commons-logging stylee way but 
>> am fairly surprised that 5.5.4 did not come with a basic setup for this.
> I tried to find a reasonable default, but there's none IMO as the
> logger implementations that Sun provides with JREs 1.4 and 1.5 are
> quite limited. The only solution would be to write a logger for java
> logging, but I'm not a big fan of that.
> -- 
> xxxxxxxxxxxxxxxxxxxxxxxxx
> Rémy Maucherat
> Developer & Consultant
> JBoss Group (Europe) SàRL
> xxxxxxxxxxxxxxxxxxxxxxxxx
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message