[
https://issues.apache.org/jira/browse/NIFI-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-6233.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> HandleHttpRequest -> File Leak if Port already Bind
> ---------------------------------------------------
>
> Key: NIFI-6233
> URL: https://issues.apache.org/jira/browse/NIFI-6233
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.8.0
> Environment: Linux Centos7 3.10.0-862.11.6.el7.x86_64
> jre1.8.0_181-amd64
> Reporter: Mermillod
> Priority: Minor
>
> When you start a HandleHttpRequest processor, and the port is already bind
> you get errors, with bulletins : as expected.
>
> However, this case implies a file leak (socks TCP). You can check it with
> netstat -an | grep TCP ou lsof.
>
> (In our case, the whole 3-nodes cluster was unavailable, the 65000 limit was
> reached in less than 1 hour).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
