Bug 1345816

Summary:	Logging handler lost due to conflict handlers in logging.properties and standalone.xml
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Takayoshi Kimura <tkimura>
Component:	Logging	Assignee:	Miroslav Sochurek <msochure>
Status:	CLOSED EOL	QA Contact:	Nikoleta Hlavickova <nziakova>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.8	CC:	brian.stansberry, jperkins, msochure
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:45:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Takayoshi Kimura 2016-06-13 09:00:13 UTC

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.

Upstream JIRA: https://issues.jboss.org/browse/WFCORE-1585