My Oracle Support Banner

ORABPEL-02178 Process Not Found. The BPEL Process "process_name" with revision 1.1 is not loaded (Doc ID 2185064.1)

Last updated on JANUARY 02, 2020

Applies to:

Oracle SOA Suite - Version 11.1.1.1.0 and later
Information in this document applies to any platform.

Symptoms

Errors like the ones below are seen continuously in the logs:

ORABPEL-02178 Process not found.
The BPEL process "process_name" with revision "1.1" is not loaded.
The process was not initialized properly, or the process was disabled.
Set the logging level to debug mode, check the log for the underlying exception trace related to this process loading problem.
at com.collaxa.cube.engine.deployment.DeploymentManager.getProcess(DeploymentManager.java:140)
at com.collaxa.cube.engine.deployment.DeploymentHelper.lookupProcess(DeploymentHelper.java:154)
at com.collaxa.cube.engine.data.CubeInstancePersistenceMgr.__load(CubeInstancePersistenceMgr.java:243)
at com.collaxa.cube.engine.data.CubeInstancePersistenceMgr.load(CubeInstancePersistenceMgr.java:153)
at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:4212)
at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:4324)
at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:1442)
at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:1430)
at com.collaxa.cube.ejb.impl.CubeActivityManagerBean.expireActivity(CubeActivityManagerBean.java:84)

and

Message handle error.
Error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the reported exception is: Process not found.
the BPEL process "process_name" with revision "1.1" is not loaded.
The process was not initialized properly, or the process was disabled.
Set the logging level to debug mode, check the log for the underlying exception trace related to this process loading problem.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the reported exception is: Process not found.
the BPEL process "process_name" with revision "1.1" is not loaded.
The process was not initialized properly, or the process was disabled.
Set the logging level to debug mode, check the log for the underlying exception trace related to this process loading problem.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:238)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:89)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:65)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:933)
at java.lang.Thread.run(Thread.java:745)

 

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.