[
https://issues.apache.org/jira/browse/NIFI-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650655#comment-16650655
]
ASF subversion and git services commented on NIFI-5686:
-------------------------------------------------------
Commit 32db43b3069b3c982b9c96576c11b447c229b360 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=32db43b ]
NIFI-5686: Updated StandardProcessScheduler so that if it fails to schedule a
Reporting Task, it re-schedules the @OnScheduled task instead of looping and
calling Thread.sleep. As it was, the single-threaded Process Scheduler was,
when calling ProcessScheduler.unschedule(), the unschedule task was not
executing because the schedule task was using the only thread. But switching
the logic to schedule the task for later and return, instead of calling
Thread.sleep and looping, we are able to avoid blocking the one thread in the
thread pool. Also, performed some trivial code cleanup and updated erroneous
links in Java-docs.
NIFI-5686: Fixed unit test in TestSocketLoadBalancedFlowFileQueue; renamed
TestProcessorLifecycle to ProcessorLifecycleIT as it is testing integration
between many components and largely focuses on high numbers of concurrent tasks
to see if it can trigger any threading bugs that may get introduced
NIFI-5686: Extended unit test timeouts
Signed-off-by: Matthew Burgess <[email protected]>
This closes #3062
> Test failure in TestStandardProcessScheduler
> --------------------------------------------
>
> Key: NIFI-5686
> URL: https://issues.apache.org/jira/browse/NIFI-5686
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.8.0
>
>
> The {{testReportingTaskDoesntKeepRunningAfterStop}} test in
> {{TestStandardProcessScheduler}} now fails. This was \{{@Ignore}} d in
> NIFI-5666 but should be addressed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
