[jboss-jira] [JBoss JIRA] (WFLY-3931) Custom formatter property changes not written to, but overriden by logging.properties

[James Perkins (JIRA)]

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

James Perkins updated WFLY-3931:
--------------------------------
    Workaround Description: Use the CLI {{write-attribute}} operation to write new properties.


> Custom formatter property changes not written to, but overriden by logging.properties
> -------------------------------------------------------------------------------------
>
>                 Key: WFLY-3931
>                 URL: https://issues.jboss.org/browse/WFLY-3931
>             Project: WildFly
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 8.1.0.Final
>         Environment: Wildfly 8.1.0.Final
>            Reporter: Vsevolod Golovanov
>            Assignee: James Perkins
>
> When you first add custom formatter with properties to standalone.xml, on server start property values get correctly resolved and written to logging.properties.
> If you change property values in standalone.xml of an existing custom formatter, that was flushed to logging.properties before, then on the next server start new values don't get written to logging.properties and formatter instance gets the old values from logging.properties.
> For properties with static values that are defined in standalone.xml there is a workaround: change the custom formatter name each time you change a property value.
> But with more dynamic properties, e.g. that rely on system properties, it's not so simple...



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)