You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Shawn Lavelle (JIRA)" <ji...@apache.org> on 2016/09/02 17:42:20 UTC
[jira] [Commented] (HIVE-6852) JDBC client connections hang at
TSaslTransport
[ https://issues.apache.org/jira/browse/HIVE-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459144#comment-15459144 ]
Shawn Lavelle commented on HIVE-6852:
-------------------------------------
This workaround doesn't seem to work with authentication set to CUSTOM. Client still hangs.
> JDBC client connections hang at TSaslTransport
> ----------------------------------------------
>
> Key: HIVE-6852
> URL: https://issues.apache.org/jira/browse/HIVE-6852
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Reporter: jay vyas
>
> I've noticed that when there is an underlying issue in connecting a client to the JDBC interface of the HiveServer2 to run queries, you get a hang after the thrift portion, at least in certain scenarios:
> Turning log4j to DEBUG, you can see the following when trying to get a connection using:
> {noformat}
> Connection jdbc = DriverManager.getConnection(this.con,"hive","password");
> "jdbc:hive2://localhost:10000/default",
> {noformat}
> The logs get to here before the hang :
> {noformat}
> 0 [main] DEBUG org.apache.thrift.transport.TSaslTransport - opening transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 0 [main] DEBUG org.apache.thrift.transport.TSaslTransport - opening transport org.apache.thrift.transport.TSaslClientTransport@219ba640
> 3 [main] DEBUG org.apache.thrift.transport.TSaslClientTransport - Sending mechanism name PLAIN and initial response of length 14
> 3 [main] DEBUG org.apache.thrift.transport.TSaslClientTransport - Sending mechanism name PLAIN and initial response of length 14
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status START and payload length 5
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status START and payload length 5
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status COMPLETE and payload length 14
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status COMPLETE and payload length 14
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Start message handled
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Start message handled
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Main negotiation loop complete
> 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Main negotiation loop complete
> 6 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: SASL Client receiving last message
> 6 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: SASL Client receiving last message
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)