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.
Verified with EAP 6.4.0.DR9.