My Oracle Support Banner

Stuck Threads when Using the Same Work Manager for Proxy and Invoked Business Service (Doc ID 1376993.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Service Bus - Version 3.0 to 11.1.1.5.0 [Release Aqualogic Service Bus to 11g]
Information in this document applies to any platform.

Symptoms

In Oracle Service Bus (OSB) the following flow has been implemented:

OSB Proxy service1 (sb or jejb) - route -> OSB Business service1

Under load, when max capacity of work manager used for Proxy service 1 and Business service 1 is reached, stuck threads are seen. This can happen with proxy services using synchronous inbound transports like sb or jejb.


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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.