Bug 900063 – Missing error message when creation of Custom Handler fails

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 900063 - (JBPAPP6-1540) Missing error message when creation of Custom Handler fails

Summary:	Missing error message when creation of Custom Handler fails

Status:	CLOSED CURRENTRELEASE

Aliases:	JBPAPP6-1540

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Web Console (Show other bugs)
Sub Component:
Version:	6.0.1
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	ER6
Target Release:	EAP 6.2.0
Assigned To:	Harald Pehl
QA Contact:	Jakub Cechacek
Docs Contact:

URL:	http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-03-19 07:56 EDT by Jan Martiska
Modified:	2015-02-01 17:59 EST (History)
CC List:	5 users (show)

See Also:
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 11:18:28 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	JBPAPP6-1540	Major	Closed	Missing error message when creation of Custom Handler fails	2016-02-04 08:04 EST

Groups: None (edit)

Description Jan Martiska 2012-03-19 07:56:24 EDT

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 16:01:43 EST

Docs QE Status: Removed: NEW

Comment 2 Jan Martiska 2013-02-22 07:13:16 EST

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 07:35:27 EDT

Error messages are present. Tested with ER6 and HAL 2.0.5.Final

Comment 4 Jakub Cechacek 2013-11-26 06:04:58 EST

Verified 6.2.0.CR3

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