complete log4j.xml file;rootCategory logs should go to rolling.log it should 
not go to server.log.


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

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

<!-- $Id: log4j.xml,v 1.26.2.2 2005/03/02 14:52:20 tdiesler Exp $ -->

<!--
   | 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 
   
     
     
     
     
     

     
       
            
   
   -->


     
     
     
     
     
      

     
       
            
   


   <!-- A size based file rolling appender  talon.prod.313.log  -->
   
     
     
     
     
     

     
       
            
   

    
   

   <!-- ============================== -->
   <!-- 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
   
     
     
     
     
     
     
     
     
     
     
     
     
     
     
            
     
   
   -->

   <!-- ================ -->
   <!-- Limit categories -->
   <!-- ================ -->

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


 
      
       <appender-ref ref="PROD"/>
   

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

   <!-- Limit apache axis to INFO as its DEBUG is even more verbose -->
   
      
   

   <!-- Limit JBoss categories -->
   
      
  


   <!-- Limit the JSR77 categories -->
   
      
   



   
     
   
        
   <!-- Limit JBoss webservice category
   
      
   
   -->

   <!-- 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.
   
     
   
   
     
   
   -->
  
   <!--
       | 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"/>
      <appender-ref ref="ROLLING_LOG"/>
   

   <!-- 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>


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

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


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to