FlowN Activity Executes in Sequence as Opposed to Parallel
(Doc ID 1314386.1)
Last updated on APRIL 23, 2019
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
***Checked for relevance on 22-Jun-2013***
Oracle® Fusion Middleware Performance and Tuning Guide 11g Release 1 (11.1.1)
Chapter 18.104.22.168 nonBlockingInvoke
when nonBlockingInvoke is set 'true' bpel engine should create a new thread to perform each branch's invoke activity in parallel. However, when FlowN (with N=3) activity makes 3 calls to a database adapter - all three invocations seem to occur sequentially as opposed to parallel.
The following error has been seen in the context of this situation under load:
The transaction became inactive when executing activity "231301-BpInv1-BpSeq8.521-4" for instance "231,301", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "ROLLEDBACK".
The reason was The execution of this instance "231301" for process "HandleNPRangeServiceItemBPELProcess" is supposed to be in an active jta transaction, the current transaction status is "ROLLEDBACK" .
Consult the system administrator regarding this error.
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
|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.|