[jboss-jira] [JBoss JIRA] (WFCORE-1585) Logging handler lost due to conflict handlers in logging.properties and standalone.xml

[Takayoshi Kimura (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Takayoshi Kimura updated WFCORE-1585:
-------------------------------------
    Attachment: logging.properties


Attached logging.properties to reproduce this issue. Just put this file under standalone/configuration and boot, we won't see the console logging.

> Logging handler lost due to conflict handlers in logging.properties and standalone.xml
> --------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1585
>                 URL: https://issues.jboss.org/browse/WFCORE-1585
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 2.0.10.Final
>            Reporter: Takayoshi Kimura
>            Assignee: James Perkins
>         Attachments: logging.properties
>
>
> Console logging doesn't work after logging subsystem init with the following configuration.
> * logging.properties is configured with ASYNC with CONSOLE handlers.
> * standalone.xml is configured with stock FILE and CONSOLE handlers.
> Background of why there is a mismatch between logging.properties and standalone.xml, EAP image for OpenShift is configured with ASYNC with CONSOLE handlers by default. But users can customize standalone.xml and apply custom configuration based on the stock standalone.xml.
> Expected result is logging configuration from standalone.xml is applied once logging subsystem come up regardless the mismatch.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)