Need to Remove Orabpel-00000 and Orabpel-05002 Error Messages from the Log File (Doc ID 1404345.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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

Symptoms

On : 11.1.1.3.0 version,

This note was created to describe the solution to an issue that provides a methodology to handle orphaned BPEL instances.

You might run into this issue when attempting to follow instructions in <NOTE:1327800.1>" title="Note">1327800.1> to remove the composite instances with faults and the following error occurs.

<Dec 3, 2011 2:49:46 AM EST> <Error> <oracle.soa.bpel.system> <BEA-000000> <an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "java.util.NoSuchElementException: Unable to update the state of composite instance with id='90019', as the instance does not exist. The state to be updated was 'Aborted'

<Dec 3, 2011 2:49:46 AM EST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-000000> <
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the reported exception is: Exception not handled by the Collaxa Cube system.
an unhandled exception has been thrown in the Collaxa Cube systemr; exception reported is: "java.util.NoSuchElementException: Unable to update the state of composite instance with id='90019', as the instance does not exist. The state to be updated was 'Aborted'


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