1 Reply Latest reply on Jul 2, 2006 11:11 PM by chris griffith

    Tomcat Logging

    Kiren Pillay Newbie

      Hi

      I am having a problem with Tomcat logging. When I run my application on a standalone Tomcat server, I am able to see all the logging output. ie.

      When I deploy the same application in Jboss 4.0.4GA, I do not see my application errors. I have added a category for the za.co classes in DEBUG mode for my application, still nothing from here gets logged.

      log4j.conf
      -----------

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

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

      <!-- $Id: log4j.xml,v 1.26.2.10 2006/04/21 17:29:20 csuconic 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 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

      -->




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








      <appender-ref ref="SCMBFILE"/>


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




      <!-- Limit Axis based webservice category -->












      <appender-ref ref="SCMBFILE" />

      <!--category name="org.jboss.security">




      </category-->

      <!-- Limit JBossWS 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="SCMBFILE"/>


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

        • 1. Re: Tomcat Logging
          chris griffith Expert

          kirenpillay,

          Did you read http://wiki.jboss.org/wiki/Wiki.jsp?page=Logging?

          Usually, logging problems are due to log4j.jar being deployed with your application. If you are using non-isolated classloader for your deployment do not put log4j.jar in your deployment. Also, it was not clear from your post, but I am assuming your posted config file was the log4j.xml in $JBOSS_SERVER/conf directory.

          If you still have problems, please post more details, and check that your xml file posts correctly so we can read it. Thanks, cgriffith