[ 
https://issues.apache.org/jira/browse/DRILL-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323240#comment-16323240
 ] 

Karthikeyan Manivannan commented on DRILL-6083:
-----------------------------------------------

The following change seems to fix the problem.

diff --git 
a/exec/java-exec/src/test/java/org/apache/drill/test/RestClientFixture.java 
b/exec/java-exec/src/test/java/org/apache/drill/test/RestClientFixture.java
index 988e7723d..09c6ba96f 100644
--- a/exec/java-exec/src/test/java/org/apache/drill/test/RestClientFixture.java
+++ b/exec/java-exec/src/test/java/org/apache/drill/test/RestClientFixture.java
@@ -55,7 +55,8 @@ public class RestClientFixture implements AutoCloseable {
   private final Client client;
 
   private RestClientFixture(ClusterFixture cluster) {
-    int port = cluster.config.getInt(ExecConstants.HTTP_PORT);
+    int port = cluster.drillbit().getWebServerPort();
+    //int port = cluster.config.getInt(ExecConstants.HTTP_PORT);
     String address = 
cluster.drillbits().iterator().next().getContext().getEndpoint().getAddress();
     String baseURL = "http://"; + address + ":" + port;

[~timothyfarkas], is this the correct approach?


> RestClientFixture does not connect to the correct webserver port
> ----------------------------------------------------------------
>
>                 Key: DRILL-6083
>                 URL: https://issues.apache.org/jira/browse/DRILL-6083
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Tools, Build & Test
>    Affects Versions: Future
>            Reporter: Karthikeyan Manivannan
>            Assignee: Karthikeyan Manivannan
>             Fix For: 1.13.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> RestClientFixture always connects to the default http port (8047) instead of 
> connecting to the webserver-port of the cluster. The cluster's webserver port 
> won't be 8047 if there are other Drillbits running when the cluster is 
> launched.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to