[
https://issues.apache.org/jira/browse/HIVE-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902458#comment-15902458
]
Hive QA commented on HIVE-16107:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12856857/HIVE-16107.1.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 10336 tests
executed
*Failed tests:*
{noformat}
org.apache.hive.jdbc.TestMultiSessionsHS2WithLocalClusterSpark.testSparkQuery
(batchId=219)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/4037/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/4037/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-4037/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12856857 - PreCommit-HIVE-Build
> 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)
