[
https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598735#comment-14598735
]
Matt Gilman commented on NIFI-720:
----------------------------------
This patch addresses the issue where the task continued to run after it was
stopped if it had originally failed to execute OnScheduled. However, I'm still
seeing some weird with the Run Schedule. I will open a separate ticket for that
work.
+1
> If Reporting Task fails to start properly and is then stopped, it can
> continue to run once it is able to start
> --------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-720
> URL: https://issues.apache.org/jira/browse/NIFI-720
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.2.0
>
> Attachments:
> 0001-NIFI-720-Ensure-that-if-Reporting-Task-stopped-while.patch
>
>
> Steps to replicate:
> Create a MonitorMemory reporting task.
> Set an invalid value for the Memory Pool
> Start the reporting task
> See that errors are logged indicating that it couldn't start properly
> Stop Reporting Task
> Change Memory Pool to a valid value
> MonitorMemory will begin to run. Clicking Start will cause two threads to now
> run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
