[
https://issues.apache.org/jira/browse/NIFI-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279185#comment-15279185
]
ASF GitHub Bot commented on NIFI-1865:
--------------------------------------
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/429#issuecomment-218318790
@ijokarumawak for future reference, you can push the changes to the same
branch and the PR will update automatically. If you decide to rebase, you can
do that as well and follow it with `git push --force`.
> PostHTTP and ListenHTTP never shutdown LeakyBucketStreamThrottler thread
> ------------------------------------------------------------------------
>
> Key: NIFI-1865
> URL: https://issues.apache.org/jira/browse/NIFI-1865
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.1
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Minor
> Fix For: 1.0.0, 0.7.0
>
>
> LeakyBucketStreamThrottler implements close and inside it it shutdowns
> executorService.
> However, ListenHTTP and PostHTTP doesn't call close, and since those
> processors create new LeakyBucketStreamThrottler instance when it is
> scheduled, it creates new thread without closing the old ones.
> It can be reproduced by repeating stop and start those processors again and
> again. You can confirm the number of threads are increasing by following
> command:
> {code}
> $ watch "ps -M |grep {nifi pid} | wc -l"
> {code}
> or using thread dump
> {code}
> $ tail -f logs/nifi-bootstrap.log |grep LeakyBucketStreamThrottler.java
> from another terminal
> $ kill -3 {nifi pid}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
