Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

ERROR FlowController Failed to capture component stats for Stats History in a brand new 1.13 instance

avatar
Contributor

Hello,

I am deploying NIFI 1.13.0 on Windows 10 and Windows Server and as soon as the instance is active it starts logging the following error:

 

 

 

2021-03-05 15:57:39,728 ERROR [Timer-Driven Process Thread-5] o.apache.nifi.controller.FlowController Failed to capture component stats for Stats History
java.lang.NullPointerException: null
at org.apache.nifi.diagnostics.SystemDiagnostics.getOpenFileHandles(SystemDiagnostics.java:224)
at org.apache.nifi.controller.FlowController.getNodeStatusSnapshot(FlowController.java:3011)
at org.apache.nifi.controller.FlowController.access$400(FlowController.java:230)
at org.apache.nifi.controller.FlowController$2.run(FlowController.java:697)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

 

 

This behavior is the same in an open box instance (without any configuration) and in secured instances (tls-toolkit); and at first glance it doesn't seem to have any impact on the behavior of the instance functionality, but it causes rapid growth of the nifi-app.log file and makes it difficult to read.

 

This error does not appear in 1.12.

 

I'll appreciate your help.

 

Thanks,

Temp

2 REPLIES 2

avatar
Explorer

facing the same issue on Windows

avatar
Contributor

Issue still present in 1.13.2. No workaround yet.

 

It appears that will be fixed in 1.14 according to Jira NIFI-8400