Having BPEL to OSB flow and OSB to BPEL flow results in a Unique Constraint (xxx_SOAINFRA.SCA_FLOW_INSTANCE_PK) Violated error
(Doc ID 2054722.1)
Last updated on AUGUST 16, 2024
Applies to:
Oracle SOA Suite - Version 12.1.3.0.0 and laterInformation in this document applies to any platform.
Symptoms
Following is the business scenario users have implemented which is failing with "ORA-00001: unique constraint (xxx_SOAINFRA.SCA_FLOW_INSTANCE_PK) violated" error.
Request message propagation:
BPEL1 ---OSB (Request Pipeline)---- [BPEL2(One way)]
Response Message Propagation:
OSB(Response Pipeline)----[BPEL2(one way)-------BPEL1
Users were observing that calls to BPEL2 from OSB are failing intermittently(50 out of 600 transactions). Sometimes it is failing at OSB request pipeline level while calling BPEL2 and sometimes it fails in the OSB response pipeline. In the OSB logs users are not finding any errors but in the SOA logs users are seeing "javax.ejb.TransactionRolledbackLocalException: Error committing transaction:
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |