[ 
https://issues.apache.org/jira/browse/NIFI-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142202#comment-15142202
 ] 

Puspendu Banerjee commented on NIFI-1501:
-----------------------------------------

[~joewitt] Emulated the behavior. It looks like , it's sporadic , please 
confirm. If so, then increasing thresholdMillis may be causing the problem. 
Please look in to : 
void 
org.apache.nifi.processors.standard.MonitorActivity.onTrigger(ProcessContext 
context, ProcessSession session)
-------------------------
            if (now >= previousSuccessMillis + thresholdMillis) {
                final boolean continual = 
context.getProperty(CONTINUALLY_SEND_MESSAGES).asBoolean();
                sendInactiveMarker = !inactive.getAndSet(true) || (continual && 
(now > lastInactiveMessage.get() + thresholdMillis));
            }
-----------------------------

> Test Monitor Activity has spurious failures
> -------------------------------------------
>
>                 Key: NIFI-1501
>                 URL: https://issues.apache.org/jira/browse/NIFI-1501
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Joseph Witt
>
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.816 sec <<< 
> FAILURE! - in org.apache.nifi.processors.standard.TestMonitorActivity
> testFirstRunNoMessages(org.apache.nifi.processors.standard.TestMonitorActivity)
>   Time elapsed: 1.321 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<1>
>       at org.junit.Assert.fail(Assert.java:88)
>       at org.junit.Assert.failNotEquals(Assert.java:834)
>       at org.junit.Assert.assertEquals(Assert.java:645)
>       at org.junit.Assert.assertEquals(Assert.java:631)
>       at 
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:330)
>       at 
> org.apache.nifi.processors.standard.TestMonitorActivity.testFirstRunNoMessages(TestMonitorActivity.java:204)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to