OSB 11g: Session Activation Under Load Causes Servers to Hang in Deadlock, Threads Stuck in TransactionManager

(Doc ID 1593172.1)

Last updated on JANUARY 18, 2017

Applies to:

Oracle Service Bus - Version and later
Information in this document applies to any platform.


 When activating a change session from the sbconsole, if there is heavy load on the servers a Java level deadlock can occur between two threads, eventually leading to all threads becoming STUCK. This can occur even if the change being activated is minor in nature, e.g. changing the operational settings of a service.


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