1 Reply Latest reply on Sep 18, 2002 4:52 PM by Martin Hubley

    Log4J and JBoss 3.0.1

    Martin Hubley Newbie

      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.