[
https://issues.apache.org/jira/browse/NIFI-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Moser updated NIFI-2626:
--------------------------------
Fix Version/s: (was: 0.8.0)
0.7.1
> LIstenHTTP leaks threads when address is already in use
> -------------------------------------------------------
>
> Key: NIFI-2626
> URL: https://issues.apache.org/jira/browse/NIFI-2626
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Jeff Storck
> Assignee: Jeff Storck
> Fix For: 1.0.0, 0.7.1
>
>
> While testing the current 1.0.0 master branch for release, I ran into a
> thread leak issue with ListenHTTP. Though not the fault of ListenHTTP
> explicitly, threads are being leaked by Jetty after attempting to bind to an
> address that is already in use. Jetty starts a thread when server.start() is
> called, but does not clean up after itself if the start() method throws an
> exception. Over time, these threads pile up and eventually the JVM will run
> out of memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
