Flow Trace Access Freezes Entire SOA Domain when composite 1000s bpel instances per flow id

(Doc ID 2271671.1)

Last updated on MAY 08, 2018

Applies to:

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


On : version, Deployment

Flow Trace Access Freezes Entire SOA Domain

Customer has a SOA cluster. Certain payloads cause Flow traces to run into several 1000s of components/references due to the # of payload elements such as order lines, etc. When someone clicks on such a flow trace, the entire domain slows down and eventually freezing completely. This requires whole domain restart to restore. It’s a critical situation as this occurred repeatedly in production during business hours. And no way for EM user to know beforehand how many component/reference instances each flow id is associated with to avoid clicking.

Not to have the whole environment crash if they click on a instance with large payload




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