nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MINIFI-435) MiNiFi - Cannot perform secured S2S with NiFi 1.5.0
Date Sun, 28 Jan 2018 11:08:00 GMT


ASF GitHub Bot commented on MINIFI-435:

GitHub user pvillard31 opened a pull request:

    MINIFI-435 - updated httpcomponents versions to match NiFi dependencies

    Thank you for submitting a contribution to Apache NiFi - MiNiFi.
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    - [ ] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are
trying to resolve? Pay particular attention to the hyphen "-" character.
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically
    - [ ] Is your initial contribution a single, squashed commit?
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check
clean install at the root nifi-minifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](

    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file
under minifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file
found under minifi-assembly?
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible.

You can merge this pull request into a Git repository by running:

    $ git pull MINIFI-435

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #113
commit 25f82e5f9c00f53f97dd370568e1d2a1c5d1e07b
Author: Pierre Villard <>
Date:   2018-01-28T11:06:39Z

    MINIFI-435 - updated httpcomponents versions to match NiFi dependencies


> MiNiFi - Cannot perform secured S2S with NiFi 1.5.0
> ---------------------------------------------------
>                 Key: MINIFI-435
>                 URL:
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: Data Transmission
>    Affects Versions: 0.4.0
>            Reporter: Pierre Villard
>            Priority: Blocker
>             Fix For: 0.5.0
> I think that, similarly to MINIFI-431, there is a dependency issue preventing the possibility
to perform S2S over HTTPS between MiNiFi 0.4.0 and NiFi 1.5.0. When trying to perform secured
S2S, I get the following exception:
> {noformat}
> 2018-01-27 22:41:57,581 WARN [Timer-Driven Process Thread-4] o.a.n.c.t.ContinuallyRunConnectableTask
RemoteGroupPort[name=IOT_Input,targets=https://...:9091/nifi] Administratively Pausing for
10 seconds due to processing failure: java.lang.RuntimeException: java.lang.NoSuchMethodError:
> java.lang.RuntimeException: java.lang.NoSuchMethodError: org.apache.http.impl.client.HttpClientBuilder.setSSLContext(Ljavax/net/ssl/SSLContext;)Lorg/apache/http/impl/client/HttpClientBuilder;
>         at org.apache.nifi.controller.AbstractPort.onTrigger(
>         at
>         at
>         at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$
>         at java.util.concurrent.Executors$
>         at java.util.concurrent.FutureTask.runAndReset(
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(
>         at java.util.concurrent.ScheduledThreadPoolExecutor$
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> Caused by: java.lang.NoSuchMethodError: org.apache.http.impl.client.HttpClientBuilder.setSSLContext(Ljavax/net/ssl/SSLContext;)Lorg/apache/http/impl/client/HttpClientBuilder;
>         at org.apache.nifi.remote.util.SiteToSiteRestApiClient.setupClient(
>         at org.apache.nifi.remote.util.SiteToSiteRestApiClient.getHttpClient(
>         at org.apache.nifi.remote.util.SiteToSiteRestApiClient.execute(
>         at org.apache.nifi.remote.util.SiteToSiteRestApiClient.execute(
>         at org.apache.nifi.remote.util.SiteToSiteRestApiClient.fetchController(
>         at org.apache.nifi.remote.util.SiteToSiteRestApiClient.getController(
>         at org.apache.nifi.remote.util.SiteToSiteRestApiClient.getController(
>         at org.apache.nifi.remote.client.SiteInfoProvider.refreshRemoteInfo(
>         at org.apache.nifi.remote.client.SiteInfoProvider.getSiteToSiteHttpPort(
>         at org.apache.nifi.remote.client.http.HttpClient.getBootstrapPeerDescription(
>         at org.apache.nifi.remote.client.PeerSelector.fetchRemotePeerStatuses(
>         at org.apache.nifi.remote.client.PeerSelector.refreshPeers(
>         at org.apache.nifi.remote.client.PeerSelector.createPeerStatusList(
>         at org.apache.nifi.remote.client.PeerSelector.getNextPeerStatus(
>         at org.apache.nifi.remote.client.http.HttpClient.createTransaction(
>         at org.apache.nifi.remote.StandardRemoteGroupPort.onTrigger(
>         at org.apache.nifi.controller.AbstractPort.onTrigger(
>         ... 10 common frames omitted{noformat}
> When doing the same between MiNiFi 0.3.0 and NiFi 1.5.0, it works as expected.
> I believe this could be related to NIFI-3954 / []
> I'll try to update the dependency to the same versions on MiNiFi side and try secured

This message was sent by Atlassian JIRA

View raw message