Bug 994699

Summary: Setting a null encoding on a OutputStreamHandler that uses setWriter sets the writer to null too
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Kyle Lape <klape>
Component: LoggingAssignee: Emmanuel Hugonnet (ehsavoie) <ehugonne>
Status: CLOSED CURRENTRELEASE QA Contact: Nikoleta Hlavickova <nziakova>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.1.0CC: ehugonne
Target Milestone: ---   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-20 07:17:11 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:
Bug Depends On:    
Bug Blocks: 994700    

Description Kyle Lape 2013-08-07 19:34:54 UTC 
An example is the ConsoleHandler. Using a target of CONSOLE uses the setWriter(wrap(System.console())) which sets the outputStream to null. The setEncoding() uses the outputStream then sets the writer. Since the outputStream is null due to the setWriter() being invoked, the writer is then set to null so no output is being written.
Comment 1 Emmanuel Hugonnet (ehsavoie) 2013-08-12 12:42:20 UTC 
https://github.com/jboss-logging/jboss-logmanager/pull/34 sent to jboss-logmanager
Comment 2 JBoss JIRA Server 2013-09-04 03:39:30 UTC 
James Perkins <jperkins> made a comment on jira LOGMGR-78

Pull request merged
Comment 3 Nikoleta Hlavickova 2014-08-20 07:17:11 UTC 
This issue is reported against older version and cannot be reproduced against latest 6.3.0. bits, which means it was fixed earlier. Therefore, we are closing this bug. Thank you for reporting this issue.