[
https://issues.apache.org/jira/browse/HIVE-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900619#comment-15900619
]
Vaibhav Gumashta commented on HIVE-16107:
-----------------------------------------
[~daijy] [~sushanth] Can you please take a look? Thanks
> JDBC: HttpClient should retry one more time on NoHttpResponseException
> ----------------------------------------------------------------------
>
> Key: HIVE-16107
> URL: https://issues.apache.org/jira/browse/HIVE-16107
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, JDBC
> Affects Versions: 2.0.1, 2.1.1
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Attachments: HIVE-16107.1.patch
>
>
> Hive's JDBC client in HTTP transport mode doesn't retry on
> NoHttpResponseException. We've seen the exception being thrown to the JDBC
> end user when used with Knox as the proxy, when Knox upgraded its jetty
> version, which has a smaller value for jetty connector idletimeout, and as a
> result closes the HTTP connection on server side. The next jdbc query on the
> client, throws a NoHttpResponseException. However, subsequent queries
> reconnect, but the JDBC driver should ideally handle this by retrying.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
