Hello Experts,   I am using org.apache.nifi.util.TestRunners in Nifi custom processor unit test cases, and code something like below..   testRunner = TestRunners.newTestRunner(O9QueueRouting.class); . . . . MockFlowFile ff = this.testRunner.enqueue(new ByteArrayInputStream(ffContents.getBytes(StandardCharsets.UTF_8))); Map<String, String> attrs = new HashMap<String, String>(); attrs.put("routingheader", "headervalue"); attrs.put("kafka.topic", "topic1"); ff.putAttributes(attrs); testRunner.run(); It was working earlier now started giving error like below - [ERROR] O9QueueRoutingTest.test:73 java.lang.RuntimeException: As of version 1.14.0, ProcessSession.commit() should be avoided when possible. See JavaDocs for explanations. Instead, use commitAsync(), commitAsync(Runnable), or commitAsync(Runnable, Consumer<Throwable>). However, if this is not possible, ProcessSession.commit() may still be used, but this must be explicitly enabled by calling TestRunner.   Any idea how this can be resolved ? How to explicitly enable by calling TestRunner ? Thanks Mahendra ... View more

Hello Experts,   I am trying to upgrade nifi from 1.12.1 version to 1.16.3. I have a script 'ECMAScript' which was working fine in 1.12.1and now behaving different in 1.16.3. Below is the portion of code giving error in 1.16 version when 'xyzId' is null. But it just logs null as expected in 1.12 version   var xyzId = flowFile.getAttribute('xyzId'); log.info(xyzId);   Below is the error in 1.16 version when null value received for above line (log.info() line throws below error) imer-Driven Process Thread-8] o.a.nifi.processors.script.ExecuteScript ExecuteScript[id=bae38131-0181-1000-29af-196312cdd9d9] ExecuteScript[id=bae38131-0181-1000-29af-196312cdd9d9] failed to process due to org.apache.nifi.processor.exception.ProcessException: java.lang.RuntimeException: java.lang.NoSuchMethodException: Can't unambiguously select between fixed arity signatures [(org.apache.nifi.logging.LogMessage), (java.lang.String)] of the method org.apache.nifi.controller.TerminationAwareLogger.info for argument types [null]; rolling back session org.apache.nifi.processor.exception.ProcessException: java.lang.RuntimeException: java.lang.NoSuchMethodException: Can't unambiguously select between fixed arity signatures [(org.apache.nifi.logging.LogMessage), (java.lang.String)] of the method org.apache.nifi.controller.TerminationAwareLogger.info for argument types [null] at org.apache.nifi.processors.script.ExecuteScript.onTrigger(ExecuteScript.java:245) at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1283) at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214) at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103) at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110) 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) Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodException: Can't unambiguously select between fixed arity signatures [(org.apache.nifi.logging.LogMessage), (java.lang.String)] of the method org.apache.nifi.controller.TerminationAwareLogger.info for argument types [null] at jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:397) at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:449) at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:406) at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:402) at jdk.nashorn.api.scripting.NashornScriptEngine.eval(NashornScriptEngine.java:155) at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:264) at org.apache.nifi.script.impl.JavascriptScriptRunner.run(JavascriptScriptRunner.java:39) at org.apache.nifi.processors.script.ExecuteScript.onTrigger(ExecuteScript.java:228) ... 11 common frames omitted Caused by: java.lang.NoSuchMethodException: Can't unambiguously select between fixed arity signatures [(org.apache.nifi.logging.LogMessage), (java.lang.String)] of the method org.apache.nifi.controller.TerminationAwareLogger.info for argument types [null] at jdk.internal.dynalink.beans.OverloadedMethod.throwAmbiguousMethod(OverloadedMethod.java:225) at jdk.nashorn.internal.scripts.Script$299$\^eval\_.:program(<eval>:13) at jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:637) at jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:494) at jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:393) ... 18 common frames omitted Any idea how to fix this? I want to avoid checking null values for logging also   Thanks Mahendra ... View more

Hello,   We are running single node nifi in 8 core machine and configured 'Maxmum Timer driven thread count' as 300. Once in a while Nifi get totally stuck (wont accept flowfiles) and also no app log will generate till we restart nifi manually.   So wondering if its due to nifi thread starvation...   In below article 'NiFi Thread starvation' section its mention that system will stuck in resource competition cycle. https://community.cloudera.com/t5/Community-Articles/NiFi-HDF-Dataflow-Optimization-Part-2-of-2/ta-p/245113   So any idea if nifi needs more threads than system available core then will there be any chance of nifi to get stuck ?     @Wynner     Thanks, Mahendra ... View more