My Oracle Support Banner

NullPointerException while engine tries to load a process containing a split-join circuit (Doc ID 1370264.1)

Last updated on MARCH 13, 2019

Applies to:

Oracle Business Process Management Suite - Version 10.3.2 and later
Information in this document applies to any platform.

Symptoms

Following error is seen while compiling a project in BPM Studio10.3.2 migrated from BPM 5.7 containing a split join circuit.



Process '/Process#Default-1.0' could not be started. Details:\njava.lang.NullPointerException

java.lang.NullPointerException
at fuego.metadata.execution.compiler.xpdl.microactivity.LinkSplitWithJoinPostCompiler.compile(LinkSplitWithJoinPostCompiler.java:50)
at fuego.metadata.execution.compiler.xpdl.microactivity.LinkSplitWithJoinPostCompiler.compile(LinkSplitWithJoinPostCompiler.java:23)
at fuego.metadata.execution.compiler.xpdl.AbstractActivityCompiler.runPostCompilers(AbstractActivityCompiler.java:163)
at fuego.metadata.execution.compiler.xpdl.AbstractActivityCompiler.compile(AbstractActivityCompiler.java:88)
at fuego.metadata.execution.compiler.ModelCompilerImpl.compile(ModelCompilerImpl.java:62)
at fuego.metadata.Process.compile(Process.java:1170)
at fuego.metadata.Process.compileProcess(Process.java:1107)
at fuego.metadata.Process.loadProcess(Process.java:947)
at fuego.metadata.Process.initProcess(Process.java:753)
at fuego.metadata.Process.forName(Process.java:190)
at fuego.server.BaseActiveProcess.getProcess(BaseActiveProcess.java:114)
at fuego.server.ActiveProcessImpl.loadMetadata(ActiveProcessImpl.java:1432)
at fuego.server.ActiveProcessImpl.loadMetadata(ActiveProcessImpl.java:1417)
at fuego.server.ActiveProcessImpl.<init>(ActiveProcessImpl.java:181)
at fuego.server.BaseActiveProcess.<init>(BaseActiveProcess.java:54)
at fuego.fengine.FEngineActiveProcess.<init>(FEngineActiveProcess.java:57)
at fuego.fengine.FEngineActiveProcess.createAndAddToMaps(FEngineActiveProcess.java:75)
at fuego.fengine.FEngineActiveProcessManager.createActiveProcess(FEngineActiveProcessManager.java:49)
at fuego.server.ActiveProcessManager.handleProcess(ActiveProcessManager.java:426)
at fuego.server.service.ActiveProcessService.startProcess(ActiveProcessService.java:136)
at fuego.server.service.ActiveProcessService.runProcessesLoader(ActiveProcessService.java:118)
at fuego.server.service.ActiveProcessService.activateProcesses(ActiveProcessService.java:88)
at fuego.fengine.service.FEngineActiveProcessService.startImpl(FEngineActiveProcessService.java:33)
at fuego.server.service.ActiveProcessService.start(ActiveProcessService.java:76)
at fuego.server.service.AbstractService.changeRunLevel(AbstractService.java:99)
at fuego.server.service.AbstractService.setRunLevel(AbstractService.java:52)
at fuego.fengine.ProcessServer$3.execute(ProcessServer.java:1511)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
at fuego.lang.JavaObject.invoke(JavaObject.java:227)
at fuego.component.Message.process(Message.java:585)
at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
at fuego.fengine.service.FEngineExecution$1.processBatch(FEngineExecution.java:110)
at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
at fuego.component.ExecutionThread.run(ExecutionThread.java:408)



In Studio, if you remove the split join circuit and then add again, this resolves the error in Studio.

This Modified project when deployed in BPM Enterprise or standalone, it is published and deployed without any errors. But when engine tries to load this process, it encounters same error again.
Due to this error, the process will be unavailable in workspace.


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.