[
https://issues.apache.org/jira/browse/MINIFICPP-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
marco polo updated MINIFICPP-306:
---------------------------------
Description: Turns out the cause is somewhat related to keep alive in that
we can't always expect NiFi to close the connection within a reasonable amount
of time. It could be upwards of 5-10 seconds before the HTTP connection is
severed. This may be a function of my overloaded test environment, but since
this is a problem that impacts large files, we should account for it and wait
until the connection is severed. (was: Turns out the cause is somewhat
related to keep alive in that we can't always expect NiFi to close the
connection within a reasonable amount of time. It could be upwards of 5-10
seconds before the HTTP connection is severed. )
> Resolve issue with Large files in HTTP transactions.
> -----------------------------------------------------
>
> Key: MINIFICPP-306
> URL: https://issues.apache.org/jira/browse/MINIFICPP-306
> Project: NiFi MiNiFi C++
> Issue Type: Sub-task
> Reporter: marco polo
> Assignee: marco polo
> Priority: Blocker
> Fix For: 0.3.0
>
>
> Turns out the cause is somewhat related to keep alive in that we can't always
> expect NiFi to close the connection within a reasonable amount of time. It
> could be upwards of 5-10 seconds before the HTTP connection is severed. This
> may be a function of my overloaded test environment, but since this is a
> problem that impacts large files, we should account for it and wait until the
> connection is severed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
