[
https://issues.apache.org/jira/browse/NIFI-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227093#comment-15227093
]
ASF GitHub Bot commented on NIFI-1690:
--------------------------------------
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/328
NIFI-1690 Changed MonitorMemory to use allowable values for pool names
- removed dead code from MonitorMemory
- added MonitorMemoryTest
- minor refactoring in MonitorMemory
- initial fix for NIFI-1731 (WARN logging) that was required by
MonitorMemoryTest
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1690
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/328.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 #328
----
commit 837e17547c40005bf867ffccfd211d2a8ef8ffed
Author: Oleg Zhurakousky <[email protected]>
Date: 2016-04-05T18:24:46Z
NIFI-1690 Changed MonitorMemory to use allowable values for pool names
- removed dead code from MonitorMemory
- added MonitorMemoryTest
- minor refactoring in MonitorMemory
- initial fix for NIFI-1731 (WARN logging) that was required by
MonitorMemoryTest
----
> Misconfigured MonitorMemory ReportingTask can not be stopped
> ------------------------------------------------------------
>
> Key: NIFI-1690
> URL: https://issues.apache.org/jira/browse/NIFI-1690
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.5.1
> Reporter: Matthew Clarke
> Assignee: Oleg Zhurakousky
> Fix For: 0.7.0
>
>
> The monitor memory reporting tasks allows the user to entire any value
> they want for the JVM memory pool. If the supplied value is not valid (NiFi
> can not find a memory pool with the supplied value), the reporting tasks
> appears to get stuck in the @onDemand state. At this point the task can not
> be stopped, edited, or deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
