You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "RaymondYap (Jira)" <ji...@apache.org> on 2021/03/15 12:21:00 UTC

[jira] [Updated] (NIFI-8321) Either add an IOException or a NoRouteToHostException on HttpClient

     [ https://issues.apache.org/jira/browse/NIFI-8321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RaymondYap updated NIFI-8321:
-----------------------------
    Summary: Either add an IOException  or a NoRouteToHostException on HttpClient  (was: Either add an IOException on HttpClient or a )

> Either add an IOException  or a NoRouteToHostException on HttpClient
> --------------------------------------------------------------------
>
>                 Key: NIFI-8321
>                 URL: https://issues.apache.org/jira/browse/NIFI-8321
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.12.1
>            Reporter: RaymondYap
>            Priority: Minor
>   Original Estimate: 24h
>          Time Spent: 10m
>  Remaining Estimate: 23h 50m
>
> * Because of the HttpClient lack of "NoRouteToHostException" exception.
> * The RemoteProcessGroup will crash Jetty, if the other site of NiFi Cluster disappear(host suddenly shutdown/ instance shutdown terminate...).
> * Although the HttpClient has thrown an "IOException" and the "StandardRemoteGroupPort", has caught the "IOException"
> * but the HttpClient never throw "NoRouteToHostException", therefore, "StandardRemoteGroupPort" will never catch the exception and still try to create http connection
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)