[jboss-jira] [JBoss JIRA] (WFLY-2995) Using a log4j appender as a custom-handler should invoke the activateOptions if required

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated WFLY-2995:
--------------------------------

    Comment: was deleted

(was: Pull request didn't work. Actual bug is in the logmanager.)

    
> Using a log4j appender as a custom-handler should invoke the activateOptions if required
> ----------------------------------------------------------------------------------------
>
>                 Key: WFLY-2995
>                 URL: https://issues.jboss.org/browse/WFLY-2995
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> 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 message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira