nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-1690) Misconfigured MonitorMemory ReportingTask can not be stopped
Date Thu, 16 Jun 2016 23:13:05 GMT

    [ https://issues.apache.org/jira/browse/NIFI-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334918#comment-15334918
] 

ASF GitHub Bot commented on NIFI-1690:
--------------------------------------

Github user alopresto commented on the issue:

    https://github.com/apache/nifi/pull/328
  
    Merged and closed. Will do the same for [PR 533](https://github.com/apache/nifi/pull/533).



> 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: 1.0.0, 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)

Mime
View raw message