[jboss-jira] [JBoss JIRA] (AS7-2318) Web Console: The log4j/log editor should assist users with configurations/settings that do not make sense
[
https://issues.jboss.org/browse/AS7-2318?page=com.atlassian.jira.plugin.s...
]
Doug Grove commented on AS7-2318:
---------------------------------
What appears in the log is determined by the loggers and handlers. The basic problem is
that the handlers are on one tab and the loggers are on another in the admin console. So
the user adds a logger at the DEBUG level, but that logging does not appear in the log as
the handler is set to INFO level. The user should be provided with an indication that
logging from a logger will not be in the log due to the level of the handler.
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