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 2019/02/14 18:30:00 UTC
[jira] [Commented] (NIFI-6031) ListenTCP processor does not release
connections if client disconnects abruptly
[ https://issues.apache.org/jira/browse/NIFI-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768603#comment-16768603 ]
ASF subversion and git services commented on NIFI-6031:
-------------------------------------------------------
Commit ae8a794ff04ce28c9cfee887981635577645e0f1 in nifi's branch refs/heads/master from Endre Zoltan Kovacs
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ae8a794 ]
NIFI-6031: allow OS level socket keep alive checking
This closes #3307.
Signed-off-by: Bryan Bende <bb...@apache.org>
> ListenTCP processor does not release connections if client disconnects abruptly
> -------------------------------------------------------------------------------
>
> Key: NIFI-6031
> URL: https://issues.apache.org/jira/browse/NIFI-6031
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.5.0
> Reporter: Endre Kovacs
> Assignee: Endre Kovacs
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If a client connected to ListenTCP processor, gets disconnected abruptly:
> (eg.: they disconnected their VPN to NiFi's network), the client-TCP-socket on the NiFi node will be seen lingering for an extended amount of time (eg.: such socket can linger in established state even after 12 hours after disconnection)
> Or till a manual workaround is done: the ListenTCP processor is restarted.
> An ideal fix would be to allow the underlying OS to poll the socket if the remote side is still alive, and disconnect it if not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)