[HADOOP-16174] Disable wildfly logs to the console

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.3.0
• Component/s: fs/azure
• Assignee: Denes Gerencser
• Reporter: Denes Gerencser
• Created: 07/Mar/19 14:41
• Updated: 07/Jun/19 14:12
• Resolved: 09/Mar/19 18:48

Description

We experience that the wildfly log

Mar 06, 2019 4:33:53 PM org.wildfly.openssl.SSL init
INFO: WFOPENSSL0002 OpenSSL Version OpenSSL 1.0.2g  1 Mar 2016

(sometimes) appears on the console but it should never. Note: this is a consequence of HADOOP-15851.
Our analysis shows the reason is that 

java.util.logging.Logger.getLogger()

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.'

Issue Links

• is related to: HADOOP-16353 Backport ABFS changes from trunk to branch-3.2
• relates to: HADOOP-15851 Disable wildfly logs to the console