[
https://issues.apache.org/jira/browse/NIFI-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941281#comment-16941281
]
William Gosse edited comment on NIFI-6661 at 9/30/19 7:42 PM:
--------------------------------------------------------------
Looking for similar issues in google these ones seem to be close:
https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-handlehttprequest-response-issue/m-p/199086
http://apache-nifi-users-list.2361937.n4.nabble.com/HandleHttpRequest-failing-td1062.html
I'm pretty sure I'm terminating all my flows with a proper HandleHtmlResponse.
I'm kind of concerned that Nifi could get a stuck thread that causes the
request handler to be non-responsive. Can't anything be done about this without
having to totally restarting Nif?
This is a rather serious issue for us. We can't have Nifi stop working for any
reason if possible especially for something like a client dropping its
connection.
was (Author: wgosse):
Looking for similar issues in google these ones seem to be close:
https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-handlehttprequest-response-issue/m-p/199086
http://apache-nifi-users-list.2361937.n4.nabble.com/HandleHttpRequest-failing-td1062.html
I'm pretty sure I'm terminating all my flows with a proper HandleHtmlResponse.
I'm kind of concerned that Nifi could get a stuck thread that causes the
request handler to be non-responsive. Can't anything be done about this without
having to totally restarting Nif?
> HandleHttpRequest - Failed to receive content from HTTP Request
> ---------------------------------------------------------------
>
> Key: NIFI-6661
> URL: https://issues.apache.org/jira/browse/NIFI-6661
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.9.2
> Reporter: William Gosse
> Priority: Major
>
> I have had couple occurrence of the following exception occurring on an
> HandleHttpRequest pprocessor:
> nifi-app_2019-09-06_12.0.log:2019-09-06 12:24:48,132 ERROR [Timer-Driven
> Process Thread-3] o.a.n.p.standard.HandleHttpRequest
> HandleHttpRequest[id=6ceef915-4430-30fa-09d2-b12bb2142172] Failed to receive
> content from HTTP Request from 108.26.163.22 due to java.io.IOException:
> java.util.concurrent.TimeoutException: Idle timeout expired: 600001/600000
> ms: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout
> expired: 600001/600000 ms
>
> When it occurs the HandleHttpRequest processor stops excepting requests and I
> have to restart nifi in order to recover.
>
> Is there anything I can do to better handle this exception?
> Also I only see this happening with one of my user who may be ealing with
> network latency.
> I have not been able to recreate the issue myself with this exact excetion
> message. However the fact the it causes HandleHttpRequest processor to stop
> functioning seems serious to me.
> The only time that ever happened to me is when it to long to get to the
> HandleHttpResponse. I currently have the Request Expiration property for my
> StandardHttpContextMap set to 10 minutes. If the this value is exceeded the
> HandleHttpRequest hangs up. In this specific issue that time out also was
> reached but it seems that the flow never got beyond the HandleHttpRequest.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
