Error While Invoking Bean Cube Engine - Running A BPEL Process With Assertion Triggers
(Doc ID 432754.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 and later
Information in this document applies to any platform.
You have a project containing BPEL Process. For example:
ProcessA - Simulates a configuration service that collects configuration parameters from
ProcessB - Invokes ProcessA and just transforms the results into an output XML.
You have a test suite which uses assertions that generates an exception on assertion failure.
Run the test suite with assertion, it shows successfully completed on BPEL Console.
- Looking at the instances in the BPEL console, the process runs OK.
- The Test framework triggers an exception at the application server.
The following error messages are seen in domain log & OPMN logs:
<ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube engine": Cannot access instance.
The action "abort" cannot be performed on the instance "190056" because of its current state
("closed.completed"). Please consult the documentation for a list of all the permissible actions that can be performed on a instance when it is in the "closed.completed" state.
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