You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Artem Anokhin (JIRA)" <ji...@apache.org> on 2019/03/27 10:39:00 UTC

[jira] [Created] (NIFI-6153) [Wait/Notify] Wait processor doesn't release a file

Artem Anokhin created NIFI-6153:
-----------------------------------

             Summary: [Wait/Notify] Wait processor doesn't release a file
                 Key: NIFI-6153
                 URL: https://issues.apache.org/jira/browse/NIFI-6153
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
    Affects Versions: 1.9.1, 1.8.0
            Reporter: Artem Anokhin
         Attachments: image-2019-03-27-13-26-08-354.png

TC:

1) Flow

!image-2019-03-27-13-26-08-354.png!

2) Wait Processor Properties:

*Release Signal Identifier:* signal_${filename}

*Target Signal Count:* 0

*Distributed Cache Service:* RedisDistributedMapCacheClientService

*Wait Mode:* Keep in the upstream connection

3) Notify Processor Properties:

*Release Signal Identifier:* signal_${filename}

*Distributed Cache Service:* RedisDistributedMapCacheClientService

*ER:*
Flow file would be released if the expected count is 0.

*AR:*
 * Without Notify processor a flowFile doesn't release.
 * With Notify processor occurs the next exception:

{code:java}
o.a.n.controller.tasks.ConnectableTask Administratively Yielding Wait[id=bea7821d-0169-1000-5107-59ea62350cd2] due to uncaught Exception: java.lang.ArithmeticException: / by zero
java.lang.ArithmeticException: / by zero
at org.apache.nifi.processors.standard.WaitNotifyProtocol$Signal.releaseCandidates(WaitNotifyProtocol.java:145)
at org.apache.nifi.processors.standard.Wait.onTrigger(Wait.java:449)
at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162)
at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:205)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)