[jira] [Commented] (NIFI-720) If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start
[ https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613329#comment-14613329 ] ASF subversion and git services commented on NIFI-720: -- Commit 8da7327188ebdb3cbadda257429e4967be07bf77 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=8da7327 ] NIFI-720: Ensure that if Reporting Task stopped while @OnScheduled method is failing that it does not start running when configuration is fixed 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)
[jira] [Commented] (NIFI-720) If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start
[ https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (NIFI-720) If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start
[
https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (NIFI-720) If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start
[ https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14598625#comment-14598625 ] Mark Payne commented on NIFI-720: - [~mcgilman] sorry, cleaned up some code and lost my 'return' statement. Attached a new patch that will hopefully work better for you :) 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)
