You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/12/29 15:12:49 UTC
[jira] [Created] (NIFI-1336) PostHTTP does not route to failure in
case of Connection failure
Mark Payne created NIFI-1336:
--------------------------------
Summary: PostHTTP does not route to failure in case of Connection failure
Key: NIFI-1336
URL: https://issues.apache.org/jira/browse/NIFI-1336
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Reporter: Mark Payne
When unable to communicate with a remote NiFi instance, PostHTTP continually rolls back the session (without penalizing) instead of routing to failure. This results in filling the logs with messages like:
2015-12-29 14:09:02,023 WARN [Timer-Driven Process Thread-11] o.a.nifi.processors.standard.PostHTTP PostHTTP[id=015d5ace-3aa3-3e51-8aae-4776d3bd3897] Failed to delete Hold that destination placed on [StandardFlowFileRecord[uuid=220fbcac-d84e-41ed-9cc7-6e558ea207ee,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1451397424256-4, container=pub1, section=4], offset=52418, length=19672005],offset=0,name=GeoLite2-City.mmdb.gz,size=19672005]] due to org.apache.http.conn.HttpHostConnectException: Connect to processing-3:5000 [processing-3/172.172.172.172] failed: Connection refused: org.apache.http.conn.HttpHostConnectException: Connect to processing-3:5000 [processing-3.demo.onyara.com/172.172.172.172] failed: Connection refused
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)