OSB, Service Callouts and OQL - Part 1
Posted
by Sabha
on Oracle Blogs
See other posts from Oracle Blogs
or by Sabha
Published on Fri, 28 Sep 2012 22:10:54 +0000
Indexed on
2012/09/29
3:47 UTC
Read the original article
Hit count: 281
/OSB
Oracle Fusion Middleware customers use Oracle Service Bus (OSB) for virtualizing Service endpoints and implementing stateless service orchestrations. Behind the performance and speed of OSB, there are a couple of key design implementations that can affect application performance and behavior under heavy load. One of the heavily used feature in OSB is the Service Callout pipeline action for message enrichment and invoking multiple services as part of one single orchestration. Overuse of this feature, without understanding its internal implementation, can lead to serious problems.
This post will delve into OSB internals, the problem associated with usage of Service Callout under high loads, diagnosing it via thread dump and heap dump analysis using tools like ThreadLogic and OQL (Object Query Language) and resolving it. The first section in the series will mainly cover the threading model used internally by OSB for implementing Route Vs. Service Callouts. Please refer to the blog post for more details.
© Oracle Blogs or respective owner