[
https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598486#comment-14598486
]
Matt Gilman commented on NIFI-720:
----------------------------------
The supplied patch did not work for me. The reporting task continues to run
even after its been stopped and using the stale values for scheduling period.
Additionally, this time when it started after correcting the Memory Pool the
following message was logged continually until it was stopped.
{code}
...
2015-06-23 18:20:27,785 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,785 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,785 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,785 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,785 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
2015-06-23 18:20:27,786 INFO [pool-20-thread-3]
o.a.n.c.s.TimerDrivenSchedulingAgent
MonitorMemory[id=e5c7e013-9f8c-450d-99bc-f1295f6924db] started.
...
{code}
> 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)
