[jira] [Created] (NIFI-2944) Validate the configured remote input hostname

["Joseph Percivall (JIRA)" <ji...@apache.org>]

Joseph Percivall created NIFI-2944:
--------------------------------------

             Summary: Validate the configured remote input hostname
                 Key: NIFI-2944
                 URL: https://issues.apache.org/jira/browse/NIFI-2944
             Project: Apache NiFi
          Issue Type: Improvement
    Affects Versions: 1.0.0
            Reporter: Joseph Percivall
            Priority: Minor


Currently NiFi doesn't do any validation on what is set for "nifi.remote.input.host". For example, I ran across 1 node cluster configured with a remote input hostname that started with a "http:// ...". This cluster started up and everything seemed fine on it's end but on the client side it failed.

After the initial connection it received "http:// ..." as the hostname for it to connect to causing UnknownHostExceptions.

NiFi should validate that the value set for the remote input host is valid in order to avoid this issue.

Example:

2016-10-25 11:18:29,132 ERROR [Timer-Driven Process Thread-6] o.a.nifi.remote.StandardRemoteGroupPort RemoteGroupPort[name=From MiNiFi,target=http://<HOSTNAME>:9090/nifi/] failed to communicate with http://<HOSTNAME>:9090/nifi/ due to java.net.UnknownHostException
2016-10-25 11:18:29,136 ERROR [Timer-Driven Process Thread-6] o.a.nifi.remote.StandardRemoteGroupPort 
java.net.UnknownHostException: null
  at sun.nio.ch.Net.translateException(Net.java:155) ~[na:1.8.0_74]
  at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:127) ~[na:1.8.0_74]
  at org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:712) ~[nifi-site-to-site-client-0.6.1.jar:0.6.1]
  at org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:685) ~[nifi-site-to-site-client-0.6.1.jar:0.6.1]
  at org.apache.nifi.remote.client.socket.EndpointConnectionPool.getEndpointConnection(EndpointConnectionPool.java:301) ~[nifi-site-to-site-client-0.6.1.jar:0.6.1]
  at org.apache.nifi.remote.client.socket.SocketClient.createTransaction(SocketClient.java:129) ~[nifi-site-to-site-client-0.6.1.jar:0.6.1]
  at org.apache.nifi.remote.StandardRemoteGroupPort.onTrigger(StandardRemoteGroupPort.java:171) ~[nifi-site-to-site-0.6.1.jar:0.6.1]
  at org.apache.nifi.controller.AbstractPort.onTrigger(AbstractPort.java:227) [nifi-framework-core-api-0.6.1.jar:0.6.1]
  at org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:81) [nifi-framework-core-0.6.1.jar:0.6.1]
  at org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:40) [nifi-framework-core-0.6.1.jar:0.6.1]
  at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123) [nifi-framework-core-0.6.1.jar:0.6.1]
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_74]
  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_74]
  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_74]
  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_74]
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_74]
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_74]
  at java.lang.Thread.run(Thread.java:745) [na:1.8.0_74]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)