Has anyone seen this or know how to work around it?
I have a webapp deployed on Tomcat 5.5.16 (FWIW, the bundled version
that came with Netbeans 5.5). In order to do its own logging, the webapp
has log4j-1.2.8.jar deployed in WEB-INF/lib/. and log4j.properties in
WEB-INF/classes/. The properties is very simple, as follows below:
# log4j configuration file
# Set root category priority to ERROR and set its only appender to A1
log4j.rootCategory=ERROR, A1
# here is the A1 appender
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d [%t] %p %c %x.%M - %m%n.
# finally, any that are set
#log4j.category.tester=DEBUG
The simple classes (a JSF backing bean and a filter) are set to use
either commons-logging or log4j directly (I tried both). In either case,
the moment that I uncomment any category line and one of my classes (the
filter or the bean) calls log.debug("some message"), Tomcat freezes
entirely. This is true whether I use log4j directly or commons-logging
in my classes, and whether or not I comment or uncomment the first
log4j.rootCategory line in log4j.properties. I get some output from the
appender matching the pattern, and then freeze. I cannot access any
context; I cannot use the manager; the only thing I can do is kill the
Tomcat process.
I am at wit's end with this; it took literally days to narrow down that
it was log4j's activation doing it.
Help?
Thanks.
--
______________________________
Avi Deitcher
[EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
