Hi all,
I had the problem that I wanted to use log4j in a webapp (based on
Spring Webflow), but I didn't want to change from the existing
jdk1.4+JULI logging of the TC server to use log4j.
When I put log4j and log4j.properties (but not commons logging) in the
webapp, with a
In the change log for TC5.5.9, there is a claim that MX4J 3.0.1 has been
integrated instead of 2. The JAR in bin from the compatibility package
for JDK1.4 matches MX4J 3.0.1. But if I put the other 3.0.1 JARs in
common/lib and configure Coyote to use jk2.properties with
mx.enabled=true, using
I have had the same problem of Tomcat not terminating and having to be
killed by hand.
It occurred with Tomcat 5.0.27, JDK1.4.2, RH Enterprise Linux 3 when I
enabled JMX via jk2 configuration.
I tried 5.0.28 but the same happened using jk2, so I put JMX on a back
burner.
Now I'm using 5.5.7,
