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

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250530#comment-13250530 ] 

James Perkins commented on WFCORE-1585:
---------------------------------------

This is likely happening because the {{ASYNC}} handler is removed which means it gets closed. Since it's closed it closes each of it's sub-handlers and since the name is the same, e.g. {{CONSOLE}}, the class name is the same and the module is the same it's not reconstructed so the writer is still closed. I'll have to think about how to solve this.

> 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.
> Most likely related to WFCORE-159.



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