[jira] [Closed] (DRILL-5589) JDBC client crashes after successful authentication if trace logging is enabled.

["Sorabh Hamirwasia (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DRILL-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sorabh Hamirwasia closed DRILL-5589.
------------------------------------

> 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
>              Labels: ready-to-commit
>             Fix For: 1.11.0
>
>
> 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)