Log4J and JBoss 3.0.1

[mhubley]

We are trying to port our application from JBoss 2.4.7 with Tomcat 4.0.4 to JBoss 3.0.1/Tomcat 4.0.4. We have extensive logging categories where each class has its own Log4J Category based on its fully-qualified classname. When I deploy our ear in 3.0.1, and configure the Log4J.xml file to have the Console Threshold as DEBUG and add a category like this:





instead of just getting debug for that category (which is what would happen in 2.4.x), I get debug output to the console for all classes in a package which start with espial. Has any one seen this behaviour before? Any ideas on what it might be? This never happened in 2.4.x, and makes our logging unusable.

Thanks,

Martin

[mhubley]

Answered my own question - if I add another category





along with the category from the previous post, it correctly only shows debug output for the espial.a.b.c category. Weird, as this extra category was not needed in 2.4.x log4j.properties. Looks like a bug?