Bug 1066606 – [GSS] (6.3.0) Using a log4j appender as a custom-handler should invoke the activateOptions if required

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1066606 - [GSS] (6.3.0) Using a log4j appender as a custom-handler should invoke the activateOptions if required

Summary:	[GSS] (6.3.0) Using a log4j appender as a custom-handler should invoke the ac...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Logging (Show other bugs)
Sub Component:
Version:	6.2.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR1
Target Release:	EAP 6.3.0
Assigned To:	James Perkins
QA Contact:	Michal Karm Babacek
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1066607
	Show dependency tree / graph

Reported:	2014-02-18 12:23 EST by Kyle Lape
Modified:	2014-06-28 11:27 EDT (History)
CC List:	4 users (show)

See Also:
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:
Clones:	1066607 (view as bug list)
Environment:
Last Closed:	2014-06-28 11:27:42 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-2995	Major	Resolved	Using a log4j appender as a custom-handler should invoke the activateOptions if required	2014-08-13 06:51:02 EDT

Groups: None (edit)

Description Kyle Lape 2014-02-18 12:23:04 EST

Currently the OptionHandler.activateOptions is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state.

Comment 2 Michal Karm Babacek 2014-03-04 05:33:50 EST

Fix is present, dummy property in place. DR1

Comment 3 Scott Mumford 2014-04-24 00:59:21 EDT

Added release note text from bug 1066607 (duplicate) written for 6.2 release and marking for inclusion in 6.3.0 documentation.

Comment 4 sgilda 2014-05-12 15:56:27 EDT

Changed <literal></literal> tags in Doc Text to ticks (`) to fix Bug 1096865

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