[
https://issues.apache.org/jira/browse/NIFI-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214230#comment-15214230
]
Matthew Clarke commented on NIFI-1690:
--------------------------------------
2016-03-28 13:53:59,950 ERROR [pool-28-thread-1]
org.apache.nifi.controller.MonitorMemory
MonitorMemory[id=847aa33d-cf08-47a8-bef9-a8d2d2fa31bb] Failed to invoke
@OnEnabled method due to org.apache.nifi.reporting.InitializationException:
Found no JVM Memory Pool with name PS Old Gen; will not monitor Memory Pool
2016-03-28 13:53:59,951 ERROR [pool-28-thread-1]
org.apache.nifi.controller.MonitorMemory
org.apache.nifi.reporting.InitializationException: Found no JVM Memory Pool
with name PS Old Gen; will not monitor Memory Pool
at
org.apache.nifi.controller.MonitorMemory.onConfigured(MonitorMemory.java:186)
~[na:na]
at sun.reflect.GeneratedMethodAccessor360.invoke(Unknown Source)
~[na:na]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:1.8.0_71]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_71]
at
org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:102)
~[nifi-framework-core-0.5.1.1.1.2.1-37.jar:0.5.1.1.1.2.1-37]
at
org.apache.nifi.controller.scheduling.StandardProcessScheduler$2.run(StandardProcessScheduler.java:210)
~[nifi-framework-core-0.5.1.1.1.2.1-37.jar:0.5.1.1.1.2.1-37]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[na:1.8.0_71]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[na:1.8.0_71]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[na:1.8.0_71]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[na:1.8.0_71]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_71]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_71]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_71]
2016-03-28 13:53:59,953 ERROR [pool-28-thread-1]
o.a.n.c.s.StandardProcessScheduler Failed to invoke the On-Scheduled Lifecycle
methods of [MonitorMemory[id=847aa33d-cf08-47a8-bef9-a8d2d2fa31bb],
java.lang.reflect.InvocationTargetException, 30 sec] due to {};
administratively yielding this ReportingTask and will attempt to schedule it
again after {}
java.lang.reflect.InvocationTargetException: null
at sun.reflect.GeneratedMethodAccessor360.invoke(Unknown Source)
~[na:na]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:1.8.0_71]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_71]
at
org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:102)
~[nifi-framework-core-0.5.1.1.1.2.1-37.jar:0.5.1.1.1.2.1-37]
at
org.apache.nifi.controller.scheduling.StandardProcessScheduler$2.run(StandardProcessScheduler.java:210)
~[nifi-framework-core-0.5.1.1.1.2.1-37.jar:0.5.1.1.1.2.1-37]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[na:1.8.0_71]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[na:1.8.0_71]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[na:1.8.0_71]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[na:1.8.0_71]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_71]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_71]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_71]
Caused by: org.apache.nifi.reporting.InitializationException: Found no JVM
Memory Pool with name PS Old Gen; will not monitor Memory Pool
at
org.apache.nifi.controller.MonitorMemory.onConfigured(MonitorMemory.java:186)
~[na:na]
... 12 common frames omitted
> 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)
