-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
Logging from server configuration (eg standalone.xml) is not used before first restart. This is described in prod doc - configuration guide:
Bootup logging configuration is specified in the logging.properties configuration file, which is active until the JBoss EAP logging subsystem is started and takes over.
If we have static final logger, this logger can't be updated (from different configuration from server configuration like standalone.xml) during runtime and server needs to be restarted (reload doesn't work)
- for example this is a case of this Narayana logger (cc rhn-engineering-mmusgrov)
Can you please evaluate this solution and consider to improve it? It would be great if logging could work properly according to server config since first start (not second one).
- relates to
-
WFCORE-2516 Changes to the logging subsystem are not persisted to the logging.properties in offline CLI
- Open