My Oracle Support Banner

Error While Invoking Bean Cube Engine - Running A BPEL Process With Assertion Triggers (Doc ID 432754.1)

Last updated on SEPTEMBER 04, 2018

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.1.0
This problem can occur on any platform.

Symptoms

You have a project containing BPEL Process.  For example:
ProcessA - Simulates a configuration service that collects configuration parameters from
a database.
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.

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

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