[
https://issues.apache.org/jira/browse/NIFI-8120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Turcsanyi updated NIFI-8120:
----------------------------------
Fix Version/s: 1.13.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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
> Fix For: 1.13.0
>
> Time Spent: 1h
> 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)
