[jboss-jira] [JBoss JIRA] (AS7-2318) Web Console: The log4j/log editor should assist users with configurations/settings that do not make sense

[David Lloyd (Resolved) (JIRA)]

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

David Lloyd resolved AS7-2318.
------------------------------

    Resolution: Rejected


I'm afraid you are incorrect.  Child logger levels override the root logger setting.

That said, the handler level overrides all, so this probably what is responsible for the effect you are seeing.  This will not change though.  The proper solution is to set the handler to the most detailed level of message you want to appear in the log file, and use per-logger levels for the rest.
                
> Web Console: The log4j/log editor should assist users with configurations/settings that do not make sense
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-2318
>                 URL: https://issues.jboss.org/browse/AS7-2318
>             Project: Application Server 7
>          Issue Type: Feature Request
>            Reporter: Jim Tyrrell
>              Labels: eap6-ux
>
> If the root logger is set to info, it will grab all of the log messages and not allow for a debug logging later on in the hierarchy.  This is a support issue as they often have users turn on more logging, but the user has not "turned off" the root logger so it is not able to grab any debug messages.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira