Bug 1066607

Summary:	[GSS] (6.2.x) 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:	Kyle Lape <klape>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikoleta Hlavickova <nziakova>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.1	CC:	brian.stansberry, cdewolf, jawilson, jperkins, klape, pkremens, smumford
Target Milestone:	CR2
Target Release:	EAP 6.2.2
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:	1066606	Environment:
Last Closed:	2014-06-02 12:49:45 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:	1066606
Bug Blocks:	1049365

Description Kyle Lape 2014-02-18 17:25:53 UTC

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 3 Scott Mumford 2014-02-27 06:20:37 UTC

This bug has been marked for inclusion in the 6.2.2 Release Notes.

To meet a PM request to have a draft of the document available for review by 4th March 2014, ECS requires assistance from someone involved with it's resolution.

If someone could review the Doc Text field above and fill out any blanks and/or correct any inaccuracies, a draft can be completed in a timely manner.

Comment 4 Scott Mumford 2014-03-03 04:04:45 UTC

Reformatted Doc Text field to prose. Will mark as fully documented after a technical review of the  Release Notes document has been performed.

(also clearing NEEDINFO flag)

Comment 5 Petr Kremensky 2014-03-04 11:21:40 UTC

Verified on EAP 6.2.2.CP.CR2