[
https://issues.jboss.org/browse/WFLY-3931?page=com.atlassian.jira.plugin....
]
Vsevolod Golovanov edited comment on WFLY-3931 at 11/29/14 4:14 PM:
--------------------------------------------------------------------
[~ander.parra], [^standalone.xml] - it's just a fresh standalone.xml with the
following added:
{code}
<formatter name="ZZZZ">
<custom-formatter class="org.jboss.logmanager.formatters.PatternFormatter"
module="org.jboss.logmanager">
<properties>
<property name="pattern" value="1" />
</properties>
</custom-formatter>
</formatter>
{code}
No more configuration or code needed to reproduce.
was (Author: vsevolodgolovanov):
[~ander.parra], here, it's just a fresh standalone.xml with the following added:
{code}
<formatter name="ZZZZ">
<custom-formatter class="org.jboss.logmanager.formatters.PatternFormatter"
module="org.jboss.logmanager">
<properties>
<property name="pattern" value="1" />
</properties>
</custom-formatter>
</formatter>
{code}
No more configuration or code needed to reproduce.
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
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...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)