]
James Perkins moved WFLY-3931 to WFCORE-474:
--------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-474 (was: WFLY-3931)
Affects Version/s: (was: 8.1.0.Final)
Component/s: Logging
(was: Logging)
Custom formatter property changes not written to, but overriden by
logging.properties
-------------------------------------------------------------------------------------
Key: WFCORE-474
URL:
https://issues.jboss.org/browse/WFCORE-474
Project: WildFly Core
Issue Type: Bug
Components: Logging
Environment: Wildfly 8.1.0.Final
Reporter: Vsevolod Golovanov
Assignee: James Perkins
Attachments: standalone.xml
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...