[
https://issues.jboss.org/browse/AS7-2246?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-2246:
-----------------------------------
Kevin,
The error was caused by changes to the valid log levels on the back end. This is now
fixed in console.
The log message does get displayed and recorded but it was easy to miss. Please put your
concerns about how error messages are presented into a separate Jira.
Log level change doesn't show error
-----------------------------------
Key: AS7-2246
URL:
https://issues.jboss.org/browse/AS7-2246
Project: Application Server 7
Issue Type: Bug
Components: Console
Reporter: Kevin Barfield
Assignee: Stan Silvert
Labels: eap6-ux
Fix For: 7.1.0.Beta1
I changed the log level for the root-logger from info to fatal. I didn't see any
change in the web console. I went to the command window and saw the following:
11:15:50,641 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 3)
Operation ("change-root-log-level") failed - address: ([("subsystem"
=> "logging")]) - failure description: "JBAS011528: Log level FATAL is
invalid."
- Is this a valid error?
- If so, the error message should show in the web console
- In general, there should be a success or error message any time there is a change
--
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