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.
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