[
https://issues.redhat.com/browse/WFCORE-2516?page=com.atlassian.jira.plug...
]
James Perkins commented on WFCORE-2516:
---------------------------------------
It could really go either way. One would expect if they boot the embedded CLI server that
the changes would be seen on the next boot. However logging is a special case where the
model would be updated, but the {{logging.properties}} file would not. So if say they
remove the console handler, on the first boot the console handler would still log messages
until the logging subsystem kicks in.
Changes to the logging subsystem are not persisted to the
logging.properties in offline CLI
-------------------------------------------------------------------------------------------
Key: WFCORE-2516
URL:
https://issues.redhat.com/browse/WFCORE-2516
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Priority: Major
When using {{embed-server}} within offline CLI changes to the logging subsystem are not
persisted to the {{logging.properties}} file.
Do note that before we fix this we may want to consider a fix for WFCORE-157. The issue
being that offline CLI is likely used to provision a server and that server may be
configured in a different location. Since the {{jboss.server.log.dir}} or other
{{relative-to}} property will be resolved and written as a fully-qualified path this could
be an issue.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)