[jboss-jira] [JBoss JIRA] (AS7-2452) Loggers can be set to invalid log level

[David Lloyd (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639095#comment-12639095 ] 

David Lloyd commented on AS7-2452:
----------------------------------

The correct behavior is for the management layer to specify the union of the JUL and log4j levels as options:

* NONE
* FATAL (log4j only)
* ERROR (log4j) and SEVERE (JUL)
* WARN (log4j) and WARNING (JUL)
* INFO (same in both)
* CONFIG (JUL only)
* DEBUG (log4j) and FINE (JUL)
* FINER (JUL only)
* TRACE (log4j) and FINEST (JUL)
* ALL

                
> Loggers can be set to invalid log level
> ---------------------------------------
>
>                 Key: AS7-2452
>                 URL: https://issues.jboss.org/browse/AS7-2452
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 7.1.0.Alpha1
>            Reporter: Stan Silvert
>            Assignee: James Perkins
>
> In CLI, the logging subystem lists the JUL logging levels as the valid choices.  However, by default the loggers in standalone.xml and domain.xml are using the Log4J levels.  This inconsistency allows loggers to have what appear to be invalid logging levels.  
> This causes a problem in the console because we fill the "levels" drop-down with the valid choices as read from dmr.  Then when we try to set the value to the "invalid" level, nothing will appear.
> Should it be considered an error if levels in standalone.xml are inconsistent with the valid levels in the management layer?

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