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.
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.
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.
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)
Verified on EAP 6.2.2.CP.CR2