[jboss-jira] [JBoss JIRA] Commented: (JBAS-5076) Loglevel TRACE doesn't work when defined in a SAR file

[Juergen Zimmermann (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-5076?page=comments#action_12397631 ] 
            
Juergen Zimmermann commented on JBAS-5076:
------------------------------------------

Uups, log4j.properties has the same issue! Wrong comment above.

> Loglevel TRACE doesn't work when defined in a SAR file
> ------------------------------------------------------
>
>                 Key: JBAS-5076
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5076
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.2.2.GA
>         Environment: WinXP SP2, JDK 1.6.0_03, JBossAS 4.2.2, JBossWS 2.0.2
>            Reporter: Juergen Zimmermann
>         Assigned To: Scott M Stark
>
> I've a SAR archive included in an EAR archive. The SAR archive contains log4j.xml (plus log4j.dtd):
> <?xml version="1.0"?>
> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
> 	<category name="de.hska">
> 		<priority value="TRACE"/>
> 	</category>
> </log4j:configuration>
> However, the TRACE level cannot be utilized in a servlet class. Using DEBUG there is no problem. I also tried to add  class="org.jboss.logging.XLevel", but the issue remains.

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