Bug 1151256 - Handlers can be created with the same name as an existing handler
Summary: Handlers can be created with the same name as an existing handler
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR9
: EAP 6.4.0
Assignee: James Perkins
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-09 23:59 UTC by James Perkins
Modified: 2019-08-19 12:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:41:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-159 0 Major Resolved Handlers can be created with the same name as an existing handler 2016-06-14 14:35:43 UTC

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.


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