SOA 11g Using bpel.config.transaction to Join a Transaction and oracle.webservices.local.optimization for Direct Java Call
(Doc ID 1332153.1)
Last updated on AUGUST 06, 2018
Applies to:Oracle(R) BPEL Process Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Having 2 composites: Client and Service that have to join the same transaction
using the parameter
<property name="bpel.config.transaction" many="false" type="xs:string">required</property>
The following behaviour can be observed:
1. If the composites are deployed on a single server or on a cluster that has the nodes on the same machine,
The behaviour is as expected:
The Service instance joins the transaction from Client.
2. If the composites are deployed on a cluster that has the nodes on different machines,
The behaviour is Not correct:
The Service instance creates a new transaction.
What is the reason for this behaviour?
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