The 'Abort' Function Fails to Stop a Running BPEL Instance in 11g

(Doc ID 1406643.1)

Last updated on NOVEMBER 08, 2017

Applies to:

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

Symptoms

Attempt to 'Abort' a running composite instance from the Enterprise Manager Console results in the instance showing as 'Terminated' but the instance actually continues to run.

One example would be a composite containing a long While loop.  An attempt to 'Abort' the instance while the loop is running will show the instance as 'Terminated' but the loop will actually complete.


How can a BPEL instance run in memory?
In order to do that you need to set the inMemoryOptimization property to true in the BPEL component in the projects that you are using.

Ex: composite.xml
<component name="SomeService">
<implementation.bpel src="SomeService.bpel"/>
<property name="bpel.config.inMemoryOptimization">true</property>
</component>

More information can be found here:
http://docs.oracle.com/cd/E21764_01/core.1111/e10108/bpel.htm#BABGIIHH

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