Bug 900063 (JBPAPP6-1540) - Missing error message when creation of Custom Handler fails
Summary: Missing error message when creation of Custom Handler fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: JBPAPP6-1540
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER6
: EAP 6.2.0
Assignee: Harald Pehl
QA Contact: Jakub Cechacek
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 11:56 UTC by Jan Martiska
Modified: 2015-02-01 22:59 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:18:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP6-1540 0 Major Closed Missing error message when creation of Custom Handler fails 2016-02-04 13:04:45 UTC

Description Jan Martiska 2012-03-19 11:56:24 UTC
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}

Comment 1 Anne-Louise Tangring 2012-11-13 21:01:43 UTC
Docs QE Status: Removed: NEW 


Comment 2 Jan Martiska 2013-02-22 12:13:16 UTC
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'

Comment 3 Harald Pehl 2013-10-25 11:35:27 UTC
Error messages are present. Tested with ER6 and HAL 2.0.5.Final

Comment 4 Jakub Cechacek 2013-11-26 11:04:58 UTC
Verified 6.2.0.CR3


Note You need to log in before you can comment on or make changes to this bug.