OSB 11g: Session Activation Under Load Causes Servers to Hang in Deadlock, Threads Stuck in TransactionManager
Last updated on FEBRUARY 06, 2018
Applies to:Oracle Service Bus - Version 18.104.22.168.0 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