Stuck Threads when Using the Same Work Manager for Proxy and Invoked Business Service

(Doc ID 1376993.1)

Last updated on JULY 13, 2018

Applies to:

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


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.




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