Andy, There is more update, I found the following bug in nifi 1.4 which is the reason for the java.lang.runtimeexception, it is looking for a keystore though there is no configuration specificed in the controller service, this is raised as an bug which was addressed in 1.5 version. But they have also provided a workaround to point the same truststore file to keystore as well, now I am no longer getting the old error, but now i see a different error, the same .jks file is working with other client applications, so any pointer to move forward will greatly appreciated.
https://issues.apache.org/jira/browse/NIFI-4655 2018-02-20 01:09:03,933 INFO [NiFi Web Server-4997] o.a.n.c.s.StandardProcessScheduler Starting InvokeHTTP[id=51f5c341-4e72-3f82-4c7a-1a93767a23b4] 2018-02-20 01:09:03,936 INFO [StandardProcessScheduler Thread-4] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled InvokeHTTP[id=51f5c341-4e72-3f82-4c7a-1a93767a23b4] to run with 1 threads 2018-02-20 01:09:03,994 ERROR [Timer-Driven Process Thread-19] o.a.nifi.processors.standard.InvokeHTTP InvokeHTTP[id=51f5c341-4e72-3f82-4c7a-1a93767a23b4] Routing to Failure due to exception: javax.net.ssl.SSLPeerUnverifiedException: Hostname <hostname> not verified: certificate: sha256/RrHmPKgr/gT1tgmUVg4H1vnObnXME+/PSaHz1gKHIdU= DN: CN=<hostname> subjectAltNames: <hostname>: javax.net.ssl.SSLPeerUnverifiedException: Hostname <hostname> not verified: certificate: sha256/RrHmPKgr/gT1tgmUVg4H1vnObnXME+/PSaHz1gKHIdU= DN: CN=atllvkafap301xd.hughestelematics.net subjectAltNames: <hostname> javax.net.ssl.SSLPeerUnverifiedException: Hostname <hostname> not verified: certificate: sha256/RrHmPKgr/gT1tgmUVg4H1vnObnXME+/PSaHz1gKHIdU= DN: CN=<hostname> subjectAltNames: <hostname> at okhttp3.internal.connection.RealConnection.connectTls(RealConnection.java:276) Regards, Jai -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
