[jboss-jira] [JBoss JIRA] Updated: (JBAS-4163) Interation between custom jboss trace and log4j trace levels

[Dimitris Andreadis (JIRA)]

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

Dimitris Andreadis updated JBAS-4163:
-------------------------------------

    Assignee: Dimitris Andreadis  (was: Scott M Stark)

Actually, I've found a better solution. Map XLevel TRACE to lower than the log4j TRACE, so both of them work:

   public static final int TRACE_INT = Level.TRACE_INT - 100;

> Interation between custom jboss trace and log4j trace levels
> ------------------------------------------------------------
>
>                 Key: JBAS-4163
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4163
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Build System, Logging
>    Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2
>            Reporter: Scott M Stark
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.0.GA,  JBossAS-5.0.0.Beta3
>
>
> I believe the following type of configuration should work with the current log4j version as it now supports trace natively:
>    <category name="org.jboss.profileservice">
>     <priority value="TRACE"/>
>     <appender-ref ref="PROFILESERVICE"/>
>    </category>
> While messages do appear in the PROFILESERVICE appender, no trace level messages are there. Most likely the jboss Logger is getting in the way of mapping this priority and an update to the common logging spi is needed.

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