Any one have idea one below error,why it is coming.
Severe errors occurred during start shape execution, terminating process.; Caused by: java.lang.NullPointerException
Please provide more info. Like what you are doing in the Start shape. Screenshot
Start shape is DISK it will pickup the files from shared disk input folder.
and the process was scheduled, only few times we are getting this error in process reporting.
I believe this error is coming because your process is scheduled and it is possible that when process is triggered there is no file on disk location to pull / read.
Dear Kartikay Nagal,
Yes i agree you, but previously we didn't get any errors like this. i am not sure why this errors getting now.
previously if no file in disk folder means process was successful with Zero zero documents.
Can you share the screenshot for disk operation? Also stack trace of error .
i have attached disk operation and debug logs also.
Can you uncheck "delete files after reading" and try if same error comes.
in general, when trying to diagnose errors with exceptions, providing the entire stack trace will speed resolution.
please find the Stack trace error details.
com.boomi.process.ProcessException: Severe errors occurred during start shape execution, terminating process.at com.boomi.process.graph.ProcessGraph.execute(ProcessGraph.java: 302)at com.boomi.process.ProcessExecution.call(ProcessExecution.java: 814)at com.boomi.execution.ExecutionTask.call(ExecutionTask.java: 936)at com.boomi.execution.ExecutionTask.call(ExecutionTask.java: 61)at com.boomi.util.concurrent.CancellableFutureTask.run(CancellableFutureTask.java: 158)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: 1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java: 615)at java.lang.Thread.run(Thread.java: 744)Caused by: java.lang.NullPointerException: null
it looks like the rest of that stack trace is missing? there should be more below the "caused by" line.
i have checked another execution and attaching stack trace below.
So it looks like there's a minor defect when handling an unexpected file listing in java. My guess as to the root cause is that the directory to which you are referring does not exist (or the atom does not have permissions to read it).
Thanks for replay, but we are using those directory from so many years.
only from last few days we are getting error on most of the processes. And process is successes some times with 0 docs.
Well i can tell you that the result is the equivalent of getting 0 docs. the fix for the defect would be essentially handling the null result the same as 0 docs. if the drive is a network mount, there could be network issues causing the directory to appear "non existent".
This occasional error happens when file system is corrupted. A start would resolve the issue. You may try this.
Sorry i couldn't understand the your point can you explain more.
The issue you have posted could be due to file system being corrupted. When you do a restart of the server most of the times the issue is resolved. You may try this if the issue still persists.
Thanks for replay, will try your sugestion.
Praveen Kumar Yasarveni
You mentioned that your process was using a Disk Connector to read files from a file share.
What is the shape immediately after the Disk Connector?
Also, in process reporting can you re-run the execution that failed and get the same error?
Does the error only happen when there are 0 files to pick up?
Retrieving data ...