Hi everyone!
I am running resin-3.0.7 and I am using latest log4j version. Everything was
fine running log4j when I had only 1 application on my server - siblumber.com.
Log4j was setup up like this - /WEB-INF/log4j.xml which uses
${user.dir}/WEB-INF/logs/logname.txt in all its appenders.
Everthing was fine up until I deployed a new application - royaleskincare.com.
It uses the EXACT same approach as siblumber.com, and here's what happens:
1. Server is started up
2. application royaleskicare.com is started up
3. its event listener configures log4j using
DOMConfigurator
4. it writes a single line into
royaleskincare.com/.../trace.txt
(everything's fine so far)
5. application siblumber.com is started up
6. its event listener configures log4j using
DOMConfigurator
7. it writes a single line into
siblumber.com/.../trace.txt
After the server is finished starting up, I check all my loggers, and it turns
out that BOTH royaleskincare.com AND siblumber.com loggers point to
"siblumber.com/.../logs/logname.txt"
It seems that when the second application starts up, it re-configures log4j for
the first application. But how is it possible? Aren't web apps ran in separate
JVMs? Even if I check System.getProperty("user.dir"),
they point to their approporiate directories.
So does log4j uses some kind of JVM-independent external configuration file
that causes it to mess up my first application?
Any help is appreciated, thanks in advance!
|
Best Regards,
Ivan V. Jouikov
(206) 228-6670
|
|
![]()
|
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 17.09.2004
|
