Are you particularly tied to 2.4.3. My development effort is targeted at JBoss3/Jetty4 at the moment. If you could confirm that the problem persists in this (you can get it from cvs - co jboss-all) I will take a look as soon as my timw allows. Otherwise it may take a while before I have time to have a look at fixing 2.4.x stuff....
If you check out the 2.4.3 branch of contrib/jetty you will see that I set up a Jetty LogSink which simply wraps log4j (I think). Perhaps something in this is causing all log4j output to be rerouted....
If you want to try compiling 2.4.3/Jetty3 from cvs you will need Jetty-3.1.3 and Jetty3Extra-1.0.1 from SourceForge.
Keep in touch,
You might want to give RH cvs a little while to settle down. Marc has just checked in a load of fundamental changes and it will take a few days for everything to bed down.
Thanks for your input. At this point, we cannot switch to JBoss3 because we are less than a month from shipping. Overall we have been thrilled with JBoss.
I will poke around in the source as you suggested. If I find out what is happening, I will post back.
Ah mystery solved. Jetty was not the culprit. We are using Tapestry and Tapestry changes the root category's settings when it starts the servlet.
Thanks again for your help!