| Summary: | Filter-spec on root-logger is not propagated into child handlers | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Petr Kremensky <pkremens> |
| Component: | Logging | Assignee: | James Perkins <jperkins> |
| Status: | CLOSED NOTABUG | QA Contact: | Nikoleta Hlavickova <nziakova> |
| Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | brian.stansberry, jholusa |
| Target Milestone: | --- | ||
| Target Release: | EAP 6.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-12 18:47:06 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: | |
This is by design currently. There is an upstream log manager issue, https://issues.jboss.org/browse/LOGMGR-45, to add support for this, but at this point filters on loggers are not inherited. The main reason being that java.util.logging does not do this either. It's best to put filters on the handlers themselves. While this would require a filter on each handler, it's really the best way to do it. Thanks for clarification James, I'll fill the BZ to mention this in Documentation. |
Description of problem: filter-spec attribute defined on root-logger is not used for child handlers (OOB: CONSOLE and FILE). Version-Release number of selected component (if applicable): EAP 6.2.0.GA How reproducible: Always Steps to Reproduce: 1. Start out-of-box standalone and connect to cli. 2. Run: /subsystem=logging/root-logger=ROOT:write-attribute(name=filter-spec, value=substituteAll("JBAS"\,"XXXXX")) 3. Reload a server Actual results: Neither console handler nor file handler take over filter-spec configuration from root logger. Expected results: User is either not allowed to define filter spec attribute on root logger, or it is propagated into all handlers registered under root logger.