[
https://issues.apache.org/jira/browse/NIFI-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431411#comment-15431411
]
ASF GitHub Bot commented on NIFI-2626:
--------------------------------------
GitHub user jtstorck opened a pull request:
https://github.com/apache/nifi/pull/910
NIFI-2626 Fixes jetty server thread leak
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jtstorck/nifi NIFI-2626
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/910.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #910
----
commit 684bbb687c3040b4a8ef9d6088b03d4a1032fe9e
Author: Jeff Storck <[email protected]>
Date: 2016-08-22T18:48:06Z
NIFI-2626 Fixes jetty server thread leak
----
> 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
>
>
> 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)
