You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/01/08 17:16:01 UTC
[jira] [Commented] (NIFI-8120) Improve HandleHttpResponse
processing of Runtime Exceptions
[ https://issues.apache.org/jira/browse/NIFI-8120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261457#comment-17261457 ]
ASF subversion and git services commented on NIFI-8120:
-------------------------------------------------------
Commit a4027e8e77facdf94817e343d88ecbfeeacbf7fc in nifi's branch refs/heads/main from exceptionfactory
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a4027e8 ]
NIFI-8120 Added RuntimeException handling on HttpContextMap.complete()
NIFI-8120 Renamed exception variable and reordered log statements
This closes #4747.
Signed-off-by: Peter Turcsanyi <tu...@apache.org>
> Improve HandleHttpResponse processing of Runtime Exceptions
> -----------------------------------------------------------
>
> Key: NIFI-8120
> URL: https://issues.apache.org/jira/browse/NIFI-8120
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.2.0, 1.12.1
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Labels: HTTP, HandleHttpResponse
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When catching a {{ProcessException}} while trying to export Flow File contents to an HTTP output stream, the {{HandleHttpResponse}} Processor will attempt to call {{HttpContextMap.complete()}} in order to finish processing the HTTP transaction. If the HTTP Context Identifier is no longer present in the {{HttpContextMap}} or if the HTTP client associated with the transaction has already terminated the connection, {{HttpContextMap.complete()}} will throw an {{IllegalStateException}} or some other type of {{RuntimeException}}. When this occurs, {{HandleHttpResponse}} falls back to administratively yielding and does not route the Flow File to the failure relationship. The end result is that Flow Files associated with closed HTTP connections remain queued.
> The other call to {{HttpContextMap.complete()}} already handles an {{IllegalStateException}} so both calls should be handled in the same way to avoid leaving files in the queue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)