Workaround In Doc ID 2394398.1 Not Acceptable
(Doc ID 2602700.1)
Last updated on MARCH 27, 2020
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Performance bottlenecks in Oracle Soa Suite 22.214.171.124.
Pattern looks like this:
A mediator component publishes to a milestone (Distributed Topic) which have multiple subscribers (BPEL composites). Each BPEL composite have multiple jms receiving threads configured.
A workaround for this was presented in Doc ID 2394398.1. This workaround is not acceptable for the customer. Reasons are:
1. Work around breaks the business flow trace and makes it hard to monitor. This is not acceptable for the operators monitoring the business critical integrations. (Orders, consignments etc)
2. There are other integration patterns where Milestone Topics are absent. Those integrations will have a different business trace behavior. This causes inconsistency across different types of customer's integrations.
Can Oracle provide a patch for this database contention issue which guarantees performance as well as consistent business flow?
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