Bug 1007333 - EAP accepts removing logging handlers even if they are referenced in ROOT logger
Summary: EAP accepts removing logging handlers even if they are referenced in ROOT logger
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.1.0,6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: DR9
: EAP 6.4.0
Assignee: James Perkins
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 09:49 UTC by Ondrej Lukas
Modified: 2019-08-19 12:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-158 0 Major Resolved Handlers should not be allowed to be removed if they're assigned to another handler or logger 2016-03-22 19:20:20 UTC

Description Ondrej Lukas 2013-09-12 09:49:13 UTC 
I think it is rather unexpected behavior than a bug. EAP in version 6.1 and 6.2 accepts removing of logging handlers even if they are referenced in ROOT logger. It caused inconsistent EAP and it could be started then. (In EAP 6.0 there is no possibility to remove referenced logging handler)

To reproduce run CLI commands:
/subsystem=logging/console-handler=CONSOLE:remove()
:reload
Comment 1 Ondrej Lukas 2013-09-12 09:57:12 UTC 
*correction, sorry about that:
"It caused inconsistent EAP and it COULDN'T be started then."
Comment 2 Nikoleta Hlavickova 2014-08-13 11:18:12 UTC 
Proposing for EAP 6.4.0 as is missed EAP 6.3.0
Comment 4 Nikoleta Hlavickova 2014-11-12 12:26:05 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.