Hello all,
I'm evaluating a switch to log4j-2 since my application is required to
rollover files by age and size (for what the composite triggering policies
come handy). The rollover files shall also be compressed, but only those
reaching a given age.
What would be the preferred approach to
Log4j currently compresses the files when it rolls them over. Of course you can
cause that to happen based on time, but it sounds like you want the time of
rollover and time of compression to be separate. If so, I am not sure you
really need to tie the compression activity to Log4j, or at
It sounds like the delaycompress option from logrotate:
http://linux.die.net/man/8/logrotate
On 9 April 2014 09:46, Ralph Goers ralph.go...@dslextreme.com wrote:
Log4j currently compresses the files when it rolls them over. Of course
you can cause that to happen based on time, but it sounds
Be aware you can't combine the RandomAccessFile appenders with logrotate. See
https://issues.apache.org/jira/browse/LOG4J2-354
Sent from my iPhone
On 2014/04/10, at 7:58, Matt Sicker boa...@gmail.com wrote:
It sounds like the delaycompress option from logrotate:
HI
I got following catalina console out continuously when I try to stop the
web application.
Brief on configuration
*version : rc1*
*Log4j2.xml*
Configuration status=OFF
Appenders
RollingRandomAccessFile name=RollingFile-${web:contextPath}
This may be caused by the LoggerContext.stop() method not being called.
Which version of Tomcat are you using? Special care is needed for Tomcat 7.0.40
and older.
A similar issue, LOG4J2-578 seemed to be caused by a config issue where the
version number in web.xml was incorrect. Can you
