- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
GetFile NullPointerException on Nifi 1.1.1
- Labels:
-
Apache NiFi
Created ‎03-23-2017 04:25 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
GetFile processor throws NullPointerException randomly on 1.1.1. Sometime it throws error and sometime it works. 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 GetFile works fine on version 0.6.1. The stacktarce is given below:
2017-03-15 12:59:46,886 ERROR [Timer-Driven Process Thread-4] o.a.nifi.processors.standard.GetFile GetFile[id=015a107a-9d19-1370-9b86-0816f7e1f7f2] Failed to retrieve files due to org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import data from /var/opt/wdp/nifi-1.1.1/deploy/flow.xml.gz for StandardFlowFileRecord[uuid=6c4b21f3-6105-480f-a1bb-d955a40d416b,claim=,offset=0,name=4327546774486623,size=0] due to java.lang.NullPointerException 2017-03-15 12:59:46,900 ERROR [Timer-Driven Process Thread-4] o.a.nifi.processors.standard.GetFile org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import data from /var/opt/wdp/nifi-1.1.1/deploy/flow.xml.gz for StandardFlowFileRecord[uuid=6c4b21f3-6105-480f-a1bb-d955a40d416b,claim=,offset=0,name=4327546774486623,size=0] due to java.lang.NullPointerException at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2649) ~[na:na] at org.apache.nifi.processors.standard.GetFile.onTrigger(GetFile.java:432) ~[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.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132) [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.runAndReset(FutureTask.java:308) [na:1.8.0_111] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_111] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [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
Created ‎06-28-2017 06:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Aveek,
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. I hope it helps.
Thanks.
Mahfuz
Created ‎06-27-2017 09:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Were you able to resolve this issue? I am getting a similar error in the putEmail processor when setting the property "Attach File" to "True".
Regards,
Aveek
Created ‎06-28-2017 06:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Aveek,
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. I hope it helps.
Thanks.
Mahfuz
