[jboss-jira] [JBoss JIRA] Closed: (JBAS-4336) Remove XLevel trace example from jboss-log4j.xml as it is not needed anymore.

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4336?page=all ]

Dimitris Andreadis closed JBAS-4336.
------------------------------------

    Resolution: Done

Comment now reads:

   <!--
      | 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.
   <category name="org.jboss.system">
     <priority value="TRACE" class="org.jboss.logging.XLevel"/>
   </category>
   <category name="org.jboss.ejb.plugins">
     <priority value="TRACE"/>
   </category>
   -->

> Remove XLevel trace example from jboss-log4j.xml as it is not needed anymore.
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4336
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4336
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.0.GA
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira