[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=17147320#comment-17147320
]
jamesqjiang commented on HIVE-6852:
---
It worked after I upgraded jdk version.
> 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
>Priority: Major
>
> 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:1/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
(v8.3.4#803005)
[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=15474070#comment-15474070
]
Shawn Lavelle commented on HIVE-6852:
-
Any thoughts on this being a known JDK issue?
https://bugs.openjdk.java.net/browse/JDK-8049846
https://bugs.openjdk.java.net/browse/JDK-8075484
> 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:1/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)
[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=15474043#comment-15474043
]
Shawn Lavelle commented on HIVE-6852:
-
Updating for CUSTOM authentication:
[code]
16/09/08 09:36:48 DEBUG TSaslTransport: opening transport
org.apache.thrift.transpor58
16/09/08 09:36:48 DEBUG TSaslClientTransport: Sending mechanism name PLAIN and
initi
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status
START an
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Writing message with status
COMPLETE
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Start message handled
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: Main negotiation loop complete
16/09/08 09:36:48 DEBUG TSaslTransport: CLIENT: SASL Client receiving last
message
[/code]
Partial Stack Trace
[code]
"main" #1 prio=5 os_prio=0 tid=0x0049f800 nid=0x409c runnable
[0x0024d000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0x000716426228> (a java.io.BufferedInputStream)
at
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:157)
[/code]
> 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:1/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)
[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:1/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)
[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=14521165#comment-14521165
]
Vladimir Kovalchuk commented on HIVE-6852:
--
The problem was that HiveServer2 conf file had authentication = NOSASL, but the
client was not prepared for this situation. Workaround is to add ";auth=noSasl"
to JDBC URL.
I would say it's definitely a bug (at protocol specification level I am afraid,
needs some re-design), and at least needs to be documentation.
> 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:1/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)
[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=14516998#comment-14516998
]
Vladimir Kovalchuk commented on HIVE-6852:
--
100% reproducible.
...
"main" #1 prio=5 os_prio=0 tid=0x01e78000 nid=0x255c runnable
[0x02bee000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
- locked <0xd63658d8> (a java.io.BufferedInputStream)
at
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at
org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178)
at
org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:288)
at
org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
at
org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:190)
at org.apache.hive.jdbc.HiveConnection.(HiveConnection.java:163)
at org.apache.hive.jdbc.HiveDriver.connect(HiveDriver.java:105)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
...
> 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:1/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)
