[jira] [Created] (HADOOP-16174) Disable wildfly logs to the console

["Denes Gerencser (JIRA)" <ji...@apache.org>]

Denes Gerencser created HADOOP-16174:
----------------------------------------

             Summary: Disable wildfly logs to the console
                 Key: HADOOP-16174
                 URL: https://issues.apache.org/jira/browse/HADOOP-16174
             Project: Hadoop Common
          Issue Type: Task
          Components: fs/azure
            Reporter: Denes Gerencser


We experience that the wildfly log
{code:java}
Mar 06, 2019 4:33:53 PM org.wildfly.openssl.SSL init
INFO: WFOPENSSL0002 OpenSSL Version OpenSSL 1.0.2g  1 Mar 2016
{code}
(sometimes) appears on the console but it should never. Note: this is a consequence of HADOOP-15851.
Our analysis shows the reason is that 
{code:java}
java.util.logging.Logger.getLogger()
{code}
is not guaranteed to always return the _same_ logger instance so SSLSocketFactoryEx may set log level on different logger object than the one used by wildfly-openssl ([https://github.com/wildfly/wildfly-openssl/blob/ace72ba07d0c746b6eb46635f4a8b122846c47c8/java/src/main/java/org/wildfly/openssl/SSL.java#L196)].
From javadoc of java.util.logging.Logger.getLogger:

'Note: The LogManager may only retain a weak reference to the newly created Logger. It is important to understand that a previously created Logger with the given name may be garbage collected at any time if there is no strong reference to the Logger. In particular, this means that two back-to-back calls like{{getLogger("MyLogger").log(...)}} may use different Logger objects named "MyLogger" if there is no strong reference to the Logger named "MyLogger" elsewhere in the program.'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org