Bug 900063 (JBPAPP6-1540)
| Summary: | Missing error message when creation of Custom Handler fails | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jan Martiska <jmartisk> |
| Component: | Web Console | Assignee: | Harald Pehl <hpehl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jakub Cechacek <jcechace> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.1 | CC: | brian.stansberry, dosoudil, hpehl, jkudrnac, rdickens |
| Target Milestone: | ER6 | ||
| Target Release: | EAP 6.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1540 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In previous JBoss EAP 6 releases, when the creation of a custom logging handler in the web management console failed, no feedback was given to the user. As a result, the user might reasonably assume that the custom logging handler was created. To resolve this issue, an error message now appears in these circumstances, making it clear to the user that the creation failed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-15 16:18:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Docs QE Status: Removed: NEW Still present in 6.1.0.DR4.
To clarify better, try to create a custom handler in the Console, and specify a non-existent module or class name. It will fail without showing an error message in the GUI.
This will appear in EAP server.log:
13:10:33,913 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 3) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "logging"),
("custom-handler" => "asdffsadg")
]): java.lang.IllegalArgumentException: JBAS011532: Failed to load module 'qq' for handler 'asdffsadg'
Error messages are present. Tested with ER6 and HAL 2.0.5.Final Verified 6.2.0.CR3 |
project_key: JBPAPP6 For example these messages should be somehow shown to the user: {noformat} "failure-description" => {"JBAS014671: Failed services" => {"jboss.logging.handler.aa" => "org.jboss.msc.service.StartException in service jboss.logging.handler.aa: JBAS011532: Could not load module blabla."}} "failure-description" => {"JBAS014671: Failed services" => {"jboss.logging.handler.aa" => "org.jboss.msc.service.StartException in service jboss.logging.handler.aa: JBAS011534: Class 'blabla' could not be found."}}, {noformat}