Bug 1151256

Summary: Handlers can be created with the same name as an existing handler
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Perkins <jperkins>
Component: LoggingAssignee: James Perkins <jperkins>
Status: CLOSED CURRENTRELEASE QA Contact: Nikoleta Hlavickova <nziakova>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: brian.stansberry, kkhan
Target Milestone: DR9   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:41:09 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:

Description James Perkins 2014-10-09 23:59:00 UTC 
Description of problem:
Handlers can be created with the same name as an existing handler. This was done to reconfigure differences in the logging subsystem XML and the logging.properties file. The problem is it will replace a handler during an ADD operation if the same name is used on another parent resource.


How reproducible:
Always

Steps to Reproduce:
1. Execute: /subsystem=logging/async-handler=CONSOLE:add(queue-length=10,overflow-action=BLOCK)

Actual results:
The handler is added and following boots fail

Expected results:
An exception should be thrown and the add should fail.
Comment 2 Nikoleta Hlavickova 2014-11-12 12:32:03 UTC 
Verified with EAP 6.4.0.DR9.