Bug 1066606
| Summary: | [GSS] (6.3.0) Using a log4j appender as a custom-handler should invoke the activateOptions if required | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Kyle Lape <klape> | |
| Component: | Logging | Assignee: | James Perkins <jperkins> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michal Karm Babacek <mbabacek> | |
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> | |
| Priority: | unspecified | |||
| Version: | 6.2.1 | CC: | kkhan, mbabacek, sgilda, smumford | |
| Target Milestone: | DR1 | |||
| Target Release: | EAP 6.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
In previous versions of JBoss EAP, changing a property in a custom-handler that was a log4j appender did not invoke the `OptionHandler.activateOptions()` on the appender if the appender implemented `OptionHandler`. It required a restart of logging resources for the change to take effect. In this release, the activation method is now invoked if properties are changed on the log4j appender and a restart is no longer required for `OptionHandler` appenders.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1066607 (view as bug list) | Environment: | ||
| Last Closed: | 2014-06-28 15:27:42 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1066607 | |||
|
Description
Kyle Lape
2014-02-18 17:23:04 UTC
Fix is present, dummy property in place. DR1 Added release note text from bug 1066607 (duplicate) written for 6.2 release and marking for inclusion in 6.3.0 documentation. Changed <literal></literal> tags in Doc Text to ticks (`) to fix Bug 1096865 |