Do you have multiple web apps in the same Tomcat using the same log4j
configuration? You should never (even with Log4j 2) have two applications use
the rolling file appender and have each try to write to the same files. What
you are experiencing is exactly what will happen.
Ralph
> On Mar
Hi Ron,
You are right! fd 1 and 2 are blocking log4j from closing the log file
properly.
tomcat starts the Java process with: java -Dblah... >> catalina.out 2>&1 &
I wonder how we did not notice this in the past years.
Thanks again
Simon
On Thu, Mar 31, 2016 at 2:38 PM, Ron Gonzalez
Simon,
To avoid confusion later on, the version of log4j you are using is 1.2.15. The
leading "1" is important because it means you're using the previous generation
of log4j, which is EOL (end of life) now. If you're doing regression testing to
upgrade to Java 8 anyway, may I suggest you
My first inclination is that you shouldn't have two locks on the same file
from the same process. That points to multiple writers independently
locking the file. This means when one tries to roll the other will still
retain the lock on the file blocking the other one.
You should identify
Greetings,
Hope someone has heard of the problem below or can suggest workarounds or
how to debug this thing.
Problem:
===
- After rolling, the old (rotated) log file continues to pick up entries
and grows.
The new log file picks up WARN and INFO level logs. The old/rolled file
picks
up
