Java Exit Code 4 in Batch Mode Despite Successful Manual Run in KNIME GUI

[akhil2698]

My workflow runs successfully when executed manually on KNIME. However, when I run it via batch mode, I encounter java exit code 4. (show screenshot)

The flow runs fully and successfully through batch mode, but still gets this issue when done executing.

Memory assigned in the config file : -Xmx48g

$knimeProcess = Start-Process -FilePath $pathToKniMe -ArgumentList “-nosave -consoleLog -reset -application org.knime.product.KNIME_BATCH_APPLICATION -workflowDir=$pathToWorkflowFolder” -RedirectStandardOutput $stdoutPath -RedirectStandardError $stderrPath -PassThru -Wait

[McReady]

Urg, they are pretty ugly and intrasparent. Please check you do not have any single node connected to the workflow which has no end, e.g. a row-filter you have implemented for tests. If so, delete these branches and try again. For me, it sovles at least 50% of these ugly startup-issues.

If it doesn’t help but you do not bother, add the " --launcher.suppressErrors" paramter to continue. But please be aware that this only suppresses the sympton and if there is another issue, you won’t be informed about it.

[akhil2698]

Thanks for the suggestion. I’ve deleted all the nodes in tthe workflow which has no end. I’ve also added try - catch error handling across my workflow, however I’m still encountering these issues.

I’d rather not use the --launcher.suppressErrors parameter.

I’m still facing the same error, could there be another reason?

[akhil2698]

@Certified-Trainers need your help on this

[ScottF]

Hi @akhil2698 -

This seems to be affecting several folks since the 5.5 release. Can you take a look at this post?

Knime 5.5 Chromium Crashing

Hi @Sarah_rushton and welcome to the forum. I see you also posted this is the 5.5 Release thread. Did you see Martin’s reply there already? While we’re working on a fix, since you’re already relying on KNIME for your scheduled workflows - have you considered our Team Plan? There’s a free trial available.

[elaisafonceca]

@ScottF

s to be affecting several folks since the 5.5 release. Can you take a look at

Hi!
I see you add a -consoleLog parameter into the script, please post here a print from the black window that appear when you execute your workflow. There you can see whatever is not working trought the execution.