You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Avish Saha (JIRA)" <ji...@apache.org> on 2017/01/28 07:45:24 UTC
[jira] [Commented] (NIFI-3383) MonitorMemory produces
UnsupportedOperationException
[ https://issues.apache.org/jira/browse/NIFI-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843968#comment-15843968 ]
Avish Saha commented on NIFI-3383:
----------------------------------
I cloned the GIT mirror for Apache NiFi (https://github.com/apache/nifi), did a build and while trying to set MonitorMemory for Eden or Survivor space, I was able to replicate this issue locally -
2017-01-28 12:32:01,275 ERROR [StandardProcessScheduler Thread-5] org.apache.nifi.controller.MonitorMemory
java.lang.UnsupportedOperationException: Usage threshold is not supported
at sun.management.MemoryPoolImpl.setUsageThreshold(MemoryPoolImpl.java:114) ~[na:1.8.0_101]
at org.apache.nifi.controller.MonitorMemory.onConfigured(MonitorMemory.java:178) ~[na:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_101]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_101]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_101]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137) ~[na:na]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125) ~[na:na]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70) ~[na:na]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47) ~[na:na]
at org.apache.nifi.controller.scheduling.StandardProcessScheduler$2.run(StandardProcessScheduler.java:213) ~[na:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_101]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
2017-01-28 12:32:01,280 ERROR [StandardProcessScheduler Thread-5] o.a.n.c.s.StandardProcessScheduler Failed to invoke the On-Scheduled Lifecycle methods of [MonitorMemory[id=e3e0dfa1-0159-1000-e04e-7a0312f0e017], 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.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_101]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_101]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_101]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137) ~[na:na]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125) ~[na:na]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70) ~[na:na]
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47) ~[na:na]
at org.apache.nifi.controller.scheduling.StandardProcessScheduler$2.run(StandardProcessScheduler.java:213) ~[na:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_101]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
Caused by: java.lang.UnsupportedOperationException: Usage threshold is not supported
at sun.management.MemoryPoolImpl.setUsageThreshold(MemoryPoolImpl.java:114) ~[na:1.8.0_101]
at org.apache.nifi.controller.MonitorMemory.onConfigured(MonitorMemory.java:178) ~[na:na]
... 16 common frames omitted
> MonitorMemory produces UnsupportedOperationException
> ----------------------------------------------------
>
> Key: NIFI-3383
> URL: https://issues.apache.org/jira/browse/NIFI-3383
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.1.1, 1.0.1
> Reporter: Bryan Bende
> Priority: Minor
> Attachments: MonitorMemory Error.png
>
>
> {code}
> [na:1.8.0_111] Caused by: java.lang.UnsupportedOperationException: Usage threshold is not supported at sun.management.MemoryPoolImpl.setUsageThreshold(MemoryPoolImpl.java:114) ~[na:1.8.0_111] at org.apache.nifi.controller.MonitorMemory.onConfigured(MonitorMemory.java:178) ~[na:na] ... 16 common frames omitted
> {code}
> MonitoryMemory checks if memoryPoolBean.isCollectionUsageThresholdSupported()) and if so it eventually calls monitoredBean.setUsageThreshold(calculatedThreshold), but setUsageThreshold then checks isUsageThresholdSupported() so it can throw UnsupportedOperationException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)