You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Sorabh Hamirwasia (JIRA)" <ji...@apache.org> on 2017/06/14 22:59:00 UTC
[jira] [Created] (DRILL-5589) JDBC client crashes after successful
authentication if trace logging is enabled.
Sorabh Hamirwasia created DRILL-5589:
----------------------------------------
Summary: JDBC client crashes after successful authentication if trace logging is enabled.
Key: DRILL-5589
URL: https://issues.apache.org/jira/browse/DRILL-5589
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.11.0
Reporter: Sorabh Hamirwasia
Assignee: Sorabh Hamirwasia
When authentication is completed then with latest changes we [dispose the saslClient instance | https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/rpc/security/AuthenticationOutcomeListener.java#L295] if encryption is not enabled. Then later in caller we try to [log the mechanism name | https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/rpc/security/AuthenticationOutcomeListener.java#L136] using saslClient instance with trace level logging. This will cause the client to crash since the saslClient instance is already disposed before logging.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)