tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "GOMEZ Henri" <>
Subject RE: logrotate and tomcat 3.3/4.0/4.1
Date Tue, 30 Apr 2002 07:33:50 GMT
>On the java side ? 
>I think we should just use commons-logging, and the admin/ 
>or manager/ or some other ( java-based code ) to control 
>the underlying logger ( which should probably default to log4j 
>when somebody has the time to do this ).

commons-logging seems a good way to hide log4j or jdk14 impl.

And is allready present in tomcat-utils which is required for
3.3.2 (may be also 4.x) 

So everything is in now ?

I do some experimentation :

I replaced ref to LogHandler with CommonLogHandler, added
a log4j.conf and put -Dlog4j.configuration=file:/$TOMCAT_HOME/conf/log4j.conf
in tomcat startup script and but tomcat didn't use log from common
(still use QueueLogger)

Question: commons-loggins should be use in QueueLogger ?

>There is no need to complicate things with -HUP and java - it
>isn't difficult ( I even started to work on that in the jk jni 
>code ), but it would be much cleaner/portable/etc to just use 
>java mechanisms. 
>( of course, JMX is a good choice - and log4j does support JMX )

In latest log4j release or in HEAD ? 

The good thing with logrotate is that it's something admins known
well and use very easily.

What about jakarta-service or it's version in commons ?

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

View raw message