[
https://issues.apache.org/jira/browse/NIFI-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431506#comment-15431506
]
ASF subversion and git services commented on NIFI-2626:
-------------------------------------------------------
Commit 184dc219b7e8a9f1c31062d6bc935abc91a94930 in nifi's branch refs/heads/0.x
from [~jtstorck]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=184dc21 ]
NIFI-2626 Fixes jetty server thread leak. This closes #910
> 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.8.0
>
>
> 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)
