After terminating Processor in DynamicallyModifiedClasspathIT system test, keep trying to empty queue until successful instead of assuming success after the first iteration.
When writing to a replacement file in AsyncCommitCallbackIT, write to a temp file and then rename. This prevents the processor from picking up the file while it's still being written.
This closes#7302
Signed-off-by: David Handermann <exceptionfactory@apache.org>
(cherry picked from commit 9f61b5f957e0389d4929fd7f4e9fd83521bcd4c5)
- Added thread naming based on Component Type and Component Identifier
This closes#7281
Signed-off-by: David Handermann <exceptionfactory@apache.org>
(cherry picked from commit a446af8aaaa7b65dd216043c847cfcb599bc83e8)
When waiting for a Processor to stop completely in system tests, also consider any terminated threads. Consider the processor stopped only when all active threads and all terminated threads have gone to 0. Additionally, when stopping all components in a Process Group, wait for the PG to reflect that there are no running components. Previously, we checked for processor active thread counts. However, this was problematic because the flow that was fetched was not fetched recursively and as a result, processors running in embedded groups were not always stopped when the waitForProcessorsStopped(String groupId) method returned. Finally, removed the step for gathering surefire-reports in failed system tests because it was not working as expected and was unneeded because the tests' logs were already gathered into the diagnostic dump that is uploaded.
Added fix for BatchFlowBetweenGroupsIT. The test would intermittently fail, based on timing. The test assumed that when Input Port in Group B was scheduled to run, it would trigger before FlowFiles in Group A finished processing. The Sleep processor caused a 10 ms delay for each of 5 FlowFiles which gives the Input Port about 50 ms to trigger. If it took longer to trigger the first time, the test failed. Adjusted the Sleep processor to use 2 seconds. So now instead of 50 milliseconds to start, it has 10 seconds. Overall this adds about 30-45 seconds to the run time of the test but ensures more-than-adequate time for the test to run, even on extremely slow hardware
This closes#7289
Signed-off-by: David Handermann <exceptionfactory@apache.org>
(cherry picked from commit 108f841525f98aab8144c0421a1ea5e5cb2a3b3b)
- Allow ProcessSession to manage its own input streams and deprecated method that reads from FlowFile without allowing it
This closes#7286
Signed-off-by: David Handermann <exceptionfactory@apache.org>
(cherry picked from commit ca2a829d47a252544a764998d11318d2a2cd6e1c)
NIFI-11557: Added an additional system test and updated github actions to include surefire-report in order to help diagnose problem that occurred in one of the last system-test runs in Github. Could not replicate problem locally
- Incremental adjustment avoids breaking test on slower environments
This closes#7260
Signed-off-by: David Handermann <exceptionfactory@apache.org>
(cherry picked from commit ec01bce20786dfef0bd457fa7de8e04edbef9589)
- Refactored Registry Filters to shared HeaderWriterHandler
- Refactored Registry Jetty Server with delegated HandlerProvider
Signed-off-by: Joe Gresock <jgresock@gmail.com>
This closes#7258.
- Upgrade applies to nifi-azure-graph-authorizer
This closes#7262
Signed-off-by: David Handermann <exceptionfactory@apache.org>
(cherry picked from commit 141ea044bb15a1848a176625293ea80fe38ed809)
- Adjusted Collection and StringUtils usage to work with Java 8
Signed-off-by: David Handermann <exceptionfactory@apache.org>
(cherry picked from commit c4f7251b23d13842618acee185e33cf6afa61317)
