It would help to see your config.
BTW, what server? And are you sure you don't have log4j.jar in the EAR (such as
APP-INF/lib under Weblogic) or in the server's lib directory? Or, there's always
the possibility of a log4j.xml sitting somewhere in the parent classloader and it
is getting picked up in preference to log4j.properties.
Jake
jchi wrote:
We have multiple WARs in a EAR. Each of the WARs includes the log4j.jar and
loads its own log4j.properties during the startup of the webapp. With this
setup, each WAR can log into its own log file.
<br>
99% of the time it is working propoerly, but there are sporadic cases where
an entry either does not get logged or get logged twice.
<br>
Has anyone run into this problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
