[
https://issues.apache.org/jira/browse/NIFI-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990202#comment-14990202
]
Mark Payne commented on NIFI-1110:
----------------------------------
Changing priority to Blocker. This indicates that there is a condition when the
queue size is not correct. This can cause a lot of weirdness, including wrong
numbers in the UI but can also result in Processors not getting scheduled to
run because they think their queue is empty. This is certainly related to the
recent refactoring of StandardFlowFIleQueue and so only will affect the
not-yet-released 0.4.0. Will look into this.
> Exception coming from FlowFileQueueSize
> ---------------------------------------
>
> Key: NIFI-1110
> URL: https://issues.apache.org/jira/browse/NIFI-1110
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.0
> Reporter: Bryan Bende
> Priority: Blocker
> Fix For: 0.4.0
>
>
> I was using the latest build of master on a CentOS 7 VM. I had a flow with
> several processors and one of them stopped with a few flow files queued in
> front. I then stopped the preceding processor and changed the expiration time
> on the queue, then started the processors and got the following exception in
> the logs:
> {code}
> java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> ~[na:1.7.0_85]
> at java.util.concurrent.FutureTask.get(FutureTask.java:188) ~[na:1.7.0_85]
> at org.apache.nifi.engine.FlowEngine.afterExecute(FlowEngine.java:100)
> ~[na:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> [na:1.7.0_85]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [na:1.7.0_85]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_85]
> Caused by: java.lang.IllegalArgumentException: null
> at org.apache.nifi.controller.queue.QueueSize.<init>(QueueSize.java:31)
> ~[nifi-api-0.3.1-SNAPSHOT.jar:0.3.1-SNAPSHOT]
> at
> org.apache.nifi.controller.StandardFlowFileQueue$FlowFileQueueSize.toQueueSize(StandardFlowFileQueue.java:1247)
> ~[na:na]
> at
> org.apache.nifi.controller.StandardFlowFileQueue.getQueueSize(StandardFlowFileQueue.java:203)
> ~[na:na]
> at
> org.apache.nifi.controller.StandardFlowFileQueue.size(StandardFlowFileQueue.java:198)
> ~[na:na]
> at
> org.apache.nifi.controller.FlowController.getGroupStatus(FlowController.java:2145)
> ~[na:na]
> at
> org.apache.nifi.controller.FlowController.getGroupStatus(FlowController.java:2030)
> ~[na:na]
> at
> org.apache.nifi.controller.FlowController.getGroupStatus(FlowController.java:2025)
> ~[na:na]
> at
> org.apache.nifi.controller.FlowController.getControllerStatus(FlowController.java:2021)
> ~[na:na]
> at
> org.apache.nifi.controller.FlowController$1.run(FlowController.java:501)
> ~[na:na]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> ~[na:1.7.0_85]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> ~[na:1.7.0_85]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> ~[na:1.7.0_85]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ~[na:1.7.0_85]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [na:1.7.0_85]
> ... 2 common frames omitted
> {code}
> Reproduced this fairly easily on the CentOS VM, but had trouble reproducing
> on my macbook.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
