Hi Remko
On 25 March 2015 at 04:21, Remko Popma remko.po...@gmail.com wrote:
So, if you specify the config location with system property
log4j.configurationFile then old log files are compressed correctly on
rollover, correct?
Correct.
I specify with the parameter
Hi Remko.
Another symptom is that the log files are not cleared on the daily archive.
I.e I started the server on Friday morning and it logs to audit.log and it
archives daily.
The audit.log file now contains all the logs since Friday and it not
cleared.
The archived logs also contain all the
Hi Remko,
Seems I found the issue.
I have two Web apps in the same container that use the same log4j2.xml and
they are in different class loaders.
I misread the docs and assumed it would work.
I am guessing there is a race condition where the one application is
writing while the other tries to
Great! Glad to hear that the problem is resolved.
-Remko
On Wed, Mar 25, 2015 at 10:30 PM, Richard Kolb rjdk...@gmail.com wrote:
Hi Remko,
Seems I found the issue.
I have two Web apps in the same container that use the same log4j2.xml and
they are in different class loaders.
I misread the
Hi Remko,
Just a quick question.
I assume one global log4j2.xml in a container is a bad idea then. Assuming
that the apps that log are in separate classloaders.
Thanks.
Richard.
Sorry, probably a silly question.
The answer is drop log4j2 in the containers lib :)
Regards,
Richard
On 25 Mar 2015 17:20, Richard Kolb rjdk...@gmail.com wrote:
Hi Remko,
Just a quick question.
I assume one global log4j2.xml in a container is a bad idea then. Assuming
that the apps that
Yes, that is the correct answer. As a matter of course you should never cause
a file to be open for write from a) multiple web applications or b) multiple
processes without using file locking. Note that RollingFileAppender clearly
says it does not support file locking - there are just too many
Can you try filePattern with a lower-case 'f' and remove the '*' characters
from the filePattern path?
For example:
FilePattern=
*logs/$${date:-MM}/fault-%d{-MM-dd_hh_mm}-%i.log.gz*
Should be
filePattern=
logs/$${date:-MM}/fault-%d{-MM-dd_hh_mm}-%i.log.gz
Regards,
Remko
Hi Remko,
Thanks, very much.
Changing FilePattern to filePattern did not solve the issue.
The * was an typeo in the email, sorry for that.
I am still experiencing the same issue inside the container and I can't
recreate the issue with the same log4j2.xml outside the container.
Next step is to
Richard,
So, if you specify the config location with system property
log4j.configurationFile then old log files are compressed correctly on
rollover, correct?
If you include the config file in your application jar and rely on the
classpath then what happens? Is rollover the only thing that
:15 +0200
Subject: Re: Intermittent log file compression issue
From: rjdk...@gmail.com
To: log4j-user@logging.apache.org
Hi Remko,
Thanks, very much.
Changing FilePattern to filePattern did not solve the issue.
The * was an typeo in the email, sorry for that.
I am still experiencing
Hello,
I am using log4j 2.2 on Windows 2008 using Java 7 and I'm experiencing an
intermittent issue where my log files used to compress, but now just move
to the archive directory uncompressed.
To debug, I changed the file pattern to be on the minute level (in bold),
and I am getting the same
12 matches
Mail list logo
