[
https://issues.apache.org/jira/browse/NIFI-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258822#comment-15258822
]
ASF GitHub Bot commented on NIFI-1814:
--------------------------------------
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/382
NIFI-1814 Extended caught exceptions
In some cases, when trying to
session.exportTo(flowFile, response.getOutputStream());
It seems that response.getOutputStream() has been somehow modified by
Jetty resulting to a FlowFileAccessException encapsulating the
EofException of Jetty.
Extended the exceptions caught and added a unit test to reproduce this
case.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-1814
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/382.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #382
----
commit 0177d8cf87abbe7cea100900a7a8412b212f3f62
Author: Pierre Villard <[email protected]>
Date: 2016-04-26T20:03:59Z
NIFI-1814 Extended caught exceptions
In some cases, when trying to
session.exportTo(flowFile, response.getOutputStream());
It seems that response.getOutputStream() has been somehow modified by
Jetty resulting to a FlowFileAccessException encapsulating the
EofException of Jetty.
Extended the exceptions caught and added a unit test to reproduce this
case.
----
> HandleHTTPResponse processor exceptions when connection is closed
> -----------------------------------------------------------------
>
> Key: NIFI-1814
> URL: https://issues.apache.org/jira/browse/NIFI-1814
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.1
> Environment: Centos 6
> Reporter: Sam Hjelmfelt
> Priority: Blocker
>
> If a HTTP connection is closed before a response is sent, the
> HandleHTTPResponse processor will throw an exception, yield due to failure,
> then try processing the rest of the events. If multiple errors happen at
> once, this compounded delay can cause cascading issues as the other
> connections timeout and close.
> Instead, the exception should be caught and the flowfile should go to the
> error relationship. A closed connection should not fail the processor, but
> instead fail the flowfile.
> Exception:
> HandleHttpResponse[id=cca1576b-5841-3fc1-b05a-5fd0f4853cb7] failed to process
> session due to org.apache.nifi.processor.exception.FlowFileAccessException:
> Failed to export
> StandardFlowFileRecord[uuid=febaedb5-4830-46b7-b0f9-71b453a4743c,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1461688143223-3, container=contS2R1,
> section=3], offset=999718,
> length=999718],offset=0,name=1628795866820216,size=999718] to
> HttpOutput@28849fc{OPEN} due to org.eclipse.jetty.io.EofException:
> org.apache.nifi.processor.exception.FlowFileAccessException: Failed to export
> StandardFlowFileRecord[uuid=febaedb5-4830-46b7-b0f9-71b453a4743c,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1461688143223-3, container=contS2R1,
> section=3], offset=999718,
> length=999718],offset=0,name=1628795866820216,size=999718] to
> HttpOutput@28849fc{OPEN} due to org.eclipse.jetty.io.EofException
> Processor Administratively Yielded for 1 sec due to processing failure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
