Are you sure you are picking up the correct config file? "log4j.xml"
is used in preference to log4j.properties even with Tomcat's
child-first classloading. If log4j.xml is on the classpath in the
default package anywhere in the classpath (server classpath or
misbehaving jars including log4j
my log4j.jar is at the WEB-INF/lib at the war
log4j.properties at WEB-INF/classes at the war
On 3/12/07, James Stauffer <[EMAIL PROTECTED]> wrote:
Where is your log4j.jar. If it is only in a shared location then the
configs are shared (basically merged together).
On 3/12/07, Andre Prasetya <[
Where is your log4j.jar. If it is only in a shared location then the
configs are shared (basically merged together).
On 3/12/07, Andre Prasetya <[EMAIL PROTECTED]> wrote:
Hi All,
I encounter a strange behaviour. I'm using commons-logging and log4j. this
is what happened.
i have an application
Hi All,
I encounter a strange behaviour. I'm using commons-logging and log4j. this
is what happened.
i have an application named heart, and a similar aplication named
md-smslogger. both using a similar log4j.properties placed at
WEB-INF/classes.
weird things happened, heart only logs to stdout
