In-Flight Process Occurs When Using Fault Management Framework With Sensors (Doc ID 561104.1)

Last updated on NOVEMBER 19, 2016

Applies to:

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

Symptoms

On 10.1.3.3.1 in Production:
When attempting to use Fault Management Framework to retry a faulted partnerlink (e.g., disabled
webservice) X number of times before finally throwing a fault, the fault is not thrown and the
process remains in-flight.

This happens when the BPEL process uses sensors.

The following error is found in <ORACLE_HOME>/bpel/domains/<domain>/logs/domain.log.


ERROR
<DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: An exception occurred during transaction completion:
; nested exception is: javax.transaction.RollbackException: returning error
in transaction:
.
Exception [TOPLINK-6004] (Oracle TopLink - 10g Release 3 (10.1.3.3.0) (Build
070608)):
.
oracle.toplink.exceptions.QueryException
Exception Description: The object
[com.collaxa.cube.engine.sensor.sa.publisher.toplink.model.ActivitySensorValue
com.collaxa.cube.engine.sensor.sa.publisher.toplink.model.ActivitySensorValue]
, with identity hashcode (System.identityHashCode()) [14,211,023],
is not from this UnitOfWork object space, but the parent session's. The
object was never registered in this UnitOfWork, but read from the parent
session and related to an object registered in the UnitOfWork.
.
Ensure that you are correctly registering your objects. If you are still
having problems, you can use the UnitOfWork.validateObjectSpace() method to
help debug where the error occurred. For more information, see the manual or
FAQ.


Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms