[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7005) Logging categories

Scott Marlow (JIRA) jira-events at lists.jboss.org
Tue Jun 9 15:36:56 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBAS-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Marlow resolved JBAS-7005.
--------------------------------

    Resolution: Done


Added additional category limits.  

This impacts what users have to do when enabling trace/debug (by changing the root logger).  To enable trace/debug for any of the classes covered by the category limits, they will also need to change the category limit to allow trace/debug.

> Logging categories
> ------------------
>
>                 Key: JBAS-7005
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7005
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>            Reporter: Jesper Pedersen
>            Assignee: Scott Marlow
>             Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
>
>
> The jboss-log4j.xml should contain categories to limit the logging of all classes used during startup.
> An example what is missing currently is
>    <!-- Limit Arjuna
>    <category name="com.arjuna">
>       <priority value="INFO"/>
>    </category>
>    -->

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

        



More information about the jboss-jira mailing list