[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: jboss-log4j.xml - category not updated at runtime

[daphnaw]

We tried to add a new category to the "Limited categories" section or change the priority value of existing category.

Following is our jboss-log4j.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<!-- ===================================================================== -->
<!--                                                                       -->
<!--  Log4j Configuration                                                  -->
<!--                                                                       -->
<!-- ===================================================================== -->

<!-- $Id: jboss-log4j.xml 62403 2007-04-18 15:26:43Z dimitris at jboss.org $ -->

<!--
   | For more configuration infromation and examples see the Jakarta Log4j
   | owebsite: http://jakarta.apache.org/log4j
 -->

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">

   <!-- ================================= -->
   <!-- Preserve messages in a local file -->
   <!-- ================================= -->

   <!-- A time/date based rolling appender -->
   
      
      
      
      

      <!-- Rollover at midnight each day -->
      <param name="DatePattern" value="'.'yyyy-MM-dd"/>

      <!-- Rollover at the top of each hour
      <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
      -->

      
         <!-- The default pattern: Date Priority [Category] Message\n -->
         

         <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
         
          -->
      
   

   <!-- A size based file rolling appender
   
     
     
     
     
     

     
       
     	    
   
   -->

   <!-- ============================== -->
   <!-- Append messages to the console -->
   <!-- ============================== -->

   
      
      
      

      
         <!-- The default pattern: Date Priority [Category] Message\n -->
         
      
   
  
   <!-- ====================== -->
   <!-- More Appender examples -->
   <!-- ====================== -->

   <!-- Buffer events and log them asynchronously
   
     
     <appender-ref ref="FILE"/>
     <appender-ref ref="CONSOLE"/>
     <appender-ref ref="SMTP"/>
   
   -->

   <!-- EMail events to an administrator
   
     
     
     
     
     
     
     
     
       
     
   
   -->

   <!-- Syslog events
   
     
     
     
     
     
       
     
   
   -->

   <!-- Log events to JMS (requires a topic to be created)
   
     
     
     
     
   
   -->

   <!-- Log events through SNMP
   
     
     
     
     
     
     
     
     
     
     
     
     
     
     
            
     
   
   -->

   <!--  Emit events as JMX notifications
   
      
      
      
      
      
      
         
      
   
   -->
   
   <!-- ================ -->
   <!-- Limit categories -->
   <!-- ================ -->

   
   <!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
   
      
   

   <!-- Limit the org.jboss.serial (jboss-serialization) to INFO as its DEBUG is verbose -->
   
      
   

   <!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
   
      
   

   <!-- Limit the jacorb category to WARN as its INFO is verbose -->
   
      
   

   <!-- Limit JBoss categories 
   
      
   
   -->

   <!-- Limit the JSR77 categories -->
   
      
   

   <!-- Enable JBossWS message tracing
   
    
   
   -->

   <!-- Decrease the priority threshold for the org.jboss.varia category
   
     
   
   -->

   <!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]
   
     
   
   -->

   <!--
      | An example of enabling the custom TRACE level priority that is used
      | by the JBoss internals to diagnose low level details. This example
      | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
      | subpackages. This will produce A LOT of logging output.
      |
      | Note: since jboss AS 4.2.x, the trace level is supported natively by
      | log4j, so although the custom org.jboss.logging.XLevel priority will
      | still work, there is no need to use it. The two examples that follow
      | will both enable trace logging.
   
     
   
   
     
   
   -->
  
   <!--
       | Logs these events to SNMP:
           - server starts/stops
           - cluster evolution (node death/startup)
           - When an EJB archive is deployed (and associated verified messages)
           - When an EAR archive is deployed
      	 
   
     
     <appender-ref ref="TRAP_LOG"/>
   
  
   
     
     <appender-ref ref="TRAP_LOG"/>
   

   
     
     <appender-ref ref="TRAP_LOG"/>
   
   
   
     
     <appender-ref ref="TRAP_LOG"/>
   
   
   
     
     <appender-ref ref="TRAP_LOG"/>
   
  
   -->

   
     
   

   
     
   
   
   
   
   <!-- ======================= -->
   <!-- Setup the Root category -->
   <!-- ======================= -->

   
      <appender-ref ref="CONSOLE"/>
      <appender-ref ref="FILE"/>
   

   <!-- Clustering logging -->
   <!-- Uncomment the following to redirect the org.jgroups and
      org.jboss.ha categories to a cluster.log file.

   
     
     
     
     
     

     
       
     
   
   
     
     <appender-ref ref="CLUSTER"/>
   
   
     
     <appender-ref ref="CLUSTER"/>
   
   -->

</log4j:configuration>




THANKS!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118305#4118305

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118305