[jboss-jira] [JBoss JIRA] Closed: (JBLOGGING-8) Updating the log4j level doesn't change the level on the corresponding JDK logger

[David Lloyd (JIRA)]

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

David Lloyd closed JBLOGGING-8.
-------------------------------

    Resolution: Done


> Updating the log4j level doesn't change the level on the corresponding JDK logger
> ---------------------------------------------------------------------------------
>
>                 Key: JBLOGGING-8
>                 URL: https://jira.jboss.org/jira/browse/JBLOGGING-8
>             Project: JBoss Logging
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jboss-logbridge
>    Affects Versions: 1.0.0.CR1-jboss-logbridge
>            Reporter: David Lloyd
>            Assignee: David Lloyd
>            Priority: Minor
>             Fix For: 1.0.0.CR2-jboss-logbridge
>
>
> This causes problems for frameworks using JDK logging which can have expensive computations performed due to a more-detailed-than-necessary log level being set on the JDK logger.  Also causes JBCTS-634 to resurface (JSF behavior changes based on log level; a bug is tripped at FINE through FINEST).

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