[
https://issues.redhat.com/browse/WFCORE-5109?page=com.atlassian.jira.plug...
]
James Perkins commented on WFCORE-5109:
---------------------------------------
I've made this a blocker as it does cause issues with the logging subsystem where the
the logging configuration is overwritten when the logging subsystem is processed. This is
an issue when something like a file handler is used and {{append}} is set to {{false}}.
The file will be closed and re-opened resulting in missing log messages.
Ensure the log manager configurator is attached to the root logger
------------------------------------------------------------------
Key: WFCORE-5109
URL:
https://issues.redhat.com/browse/WFCORE-5109
Project: WildFly Core
Issue Type: Bug
Components: Bootable JAR, Logging
Reporter: James Perkins
Assignee: James Perkins
Priority: Blocker
Fix For: 13.0.0.Final
The entry point for the bootable JAR configures a custom log context. The logging
subsystem looks on the root logger of that context to locate the {{Configurator}} which
was used to configure the context. The configurator should be attached to the root logger
so the subsystem locate it. Without this the context will be reconfigured resulting in
possible truncation of log messages.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)