[
https://issues.apache.org/jira/browse/NIFI-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226205#comment-15226205
]
Oleg Zhurakousky commented on NIFI-1690:
----------------------------------------
I am not sure I understand this issue as I can not reproduce it as described.
If "unsupported value" is provided the InitializationException is thrown
telling user exactly what is wrong. The reporting task can be stopped, fixed
and re-started. There are no deadlocks or hanging threads. In other words it
works as expected.
That said, there is room for improvement where we can definitely convert
"Memory Pool" to allowable values.
> 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)
