logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Park <simon_park_m...@yahoo.co.uk>
Subject Re: Tomcat Daily Log Rotation fails at app. level.
Date Wed, 19 May 2010 18:20:49 GMT
Hi Ryan,

Not sure whether this helps you or not, but the TimeAndSizeRollingAppender has a RollOnStartup
switch.  This ensures that logs are rolled when the appender receives the first event logged
by the application following start-up.  Thereafter logs are rolled normally according to the
time and/or size constraints that you specify.  See my homepage, www.simonsite.org.uk for

Best Regards,


From: "russo@albany.edu" <russo@albany.edu>
To: log4j-user@logging.apache.org
Sent: Wed, 19 May, 2010 18:59:03
Subject: Tomcat Daily Log Rotation fails at app. level.

Hi All:

*I solved my own issue. Sending to list in hopes it help someone else*

  This may be more of a Tomcat question...

  However, I suspect my problem relates to how Log4J is maintaining
  the state info, for when to rotate the logs.

  Running on Red Hat ES 5.5
  I have Tomcat 6.0.26 configured to use Log4j.
  This has allowed me to auto rotate the delivered logs:

Works great.

  We are running a third party web app that has stability issues so we
restart Tomcat nightly.  The server level log rotation still works.

  However, when the same setup is applied at the application level the
application log fails to rotate *Daily*.

  During testing rotation works when the FileNamePattern is configured to
have the log roll over *inside* of a given day (hourly or every minute).

<rollingPolicy class="org.apache.log4j.rolling.TimeBasedRollingPolicy">
      <param name="FileNamePattern"

Evidence suggests that Log4J is losing the state of when to roll the
application's log due to the server restart.

  In our devel. environment I disabled the nightly restart and the
application's log rotated.

What I don't understand is why the Server level log rotation still works
but, the app's log does not.

  Oh.... amazing how putting your thoughts down can sometimes resolve
   I believe, since Log4J determines when to rotate the Log based on
the rotation period when a new event is received, it is receiving
events during the shutdown and rotating the catalina.out log.

   However, the application is only used during office hours and never
receives an event prior to the restart.

The quick fix is to force an event in the application log prior to the
restart of Tomcat.

  Ideally (for my situation anyway) would be for
org.apache.log4j.rolling.TimeBasedRollingPolicy  code to cache the
policy to disk so the state of when to rotate is not lost.

    Ryan Russo -:- russo (at) albany (dot) edu
University at Albany -:- Technical Services Team

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

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