Member since
06-27-2017
6
Posts
0
Kudos Received
0
Solutions
07-26-2017
07:51 AM
I have the following EvaluateJsonPath processor which creates some new attributes for every flow file - Going forward, the attributes store some string values (which may contain spaces/special characters). I want to pass these attributes (for every flowfile in queue respectively) to an ExecuteStreamCommand processor running an R script at the backend. Handling arguments in R script -(see attachment) But every time an invalid null character error is encountered as below - 2017-07-25 19:06:33,530 ERROR [Timer-Driven Process Thread-6] o.a.n.p.standard.ExecuteStreamCommand ExecuteStreamCommand[id=7912c788-015d-1000-b1aa-73e854d7b33a] Failed to process session due to org.apache.nifi.processor.exception.ProcessException: java.io.IOException: invalid null character in command: {}
org.apache.nifi.processor.exception.ProcessException: java.io.IOException: invalid null character in command
at org.apache.nifi.processors.standard.ExecuteStreamCommand.onTrigger(ExecuteStreamCommand.java:339)
at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1120)
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
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:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: invalid null character in command
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1024)
at org.apache.nifi.processors.standard.ExecuteStreamCommand.onTrigger(ExecuteStreamCommand.java:336)
... 12 common frames omitted How to resolve the same? Attachments: evaluatejsonpath.jpg
executecommand.jpg rscript.jpg
... View more
Labels:
- Labels:
-
Apache NiFi
07-20-2017
09:52 AM
Missed the screenshot above.
... View more
07-20-2017
09:51 AM
@rbiswas Thanks for your response. 1. Yes, nifi is running on port 8080. (Verification - Able to access nifi inside the instance by navigating to localhost:8080/nifi) 2. I have opened up port 8080 in the security groups. Screenshot below -
... View more
07-18-2017
07:32 PM
I have installed the binaries of Apache NiFi 1.3.0 on an AWS Windows 2012 ec2 instance. In the security groups, I have allowed TCP connection on port 8080. However, I am still unable to access the NiFi UI from my local machine using the Public DNS of the instance. I have tried using - http://<public DNS>:8080/nifi Any help would be appreciated.
... View more
Labels:
- Labels:
-
Apache NiFi
06-27-2017
09:42 AM
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
... View more