Support Questions

Find answers, ask questions, and share your expertise

GetFTP NullPointerException on Nifi 1.1.1

avatar
Explorer

GetFTP processor throws NullPointerException randomly on 1.1.1. Recently we have installed the version 1.1.1. We have another server where nifi version 0.6.1 is running. According to our observation GetFTP works fine on version 0.6.1. To replicate the flows we have copied the flow.xml.gz file from nifi 0.6.1 to 1.1.1.Our custom processors are using the API version 0.6.1 in the project. The stacktarce is given below:

2017-03-09 02:00:02,467 ERROR [Timer-Driven Process Thread-8] o.apache.nifi.processors.standard.GetFTP GetFTP[id=1485b432-05c4-463d-a5f2-6ef76840ca6b] Unable to retrieve file /FTP_SERVER/agcd/precip/data/IDCKZRDAT0_precip_total_r005_20160806_20160806.nc due to java.lang.NullPointerException: org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0] due to java.lang.NullPointerException 2017-03-09 02:00:02,471 ERROR [Timer-Driven Process Thread-8] o.apache.nifi.processors.standard.GetFTP org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0] due to java.lang.NullPointerException at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2690) ~[na:na] at org.apache.nifi.processors.standard.GetFileTransfer.onTrigger(GetFileTransfer.java:194) ~[nifi-standard-processors-1.1.1.jar:1.1.1] at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) [nifi-api-1.1.1.jar:1.1.1] at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099) [nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136) [nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47) [nifi-framework-core-1.1.1.jar:1.1.1] at org.apache.nifi.controller.scheduling.QuartzSchedulingAgent$2.run(QuartzSchedulingAgent.java:165) [nifi-framework-core-1.1.1.jar:1.1.1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_111] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_111] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_111] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_111] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]

Caused by: java.lang.NullPointerException: null

1 ACCEPTED SOLUTION

avatar
Explorer

I have resolved this issue. I have migrated from nifi 0.6.1 to 1.1.1 but was using the old nar packer (nifi-standard-services-api-nar) in the project's pom. That's why I was having weird issue. Moving to the version 1.1.1 of nifi-standard-services-api-nar fixed the issue.

View solution in original post

1 REPLY 1

avatar
Explorer

I have resolved this issue. I have migrated from nifi 0.6.1 to 1.1.1 but was using the old nar packer (nifi-standard-services-api-nar) in the project's pom. That's why I was having weird issue. Moving to the version 1.1.1 of nifi-standard-services-api-nar fixed the issue.