Last updated on APRIL 13, 2017
Applies to:Oracle Service Bus - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Under load the Service Bus instance becomes unresponsive due to all available threads being in a 'STUCK' state.
Thread dumps show hundreds of threads with the following stack:
What's happening is that thread 13 has acquired the semaphore permit that thread 31 is waiting on. At the same time, thread 31 has acquired the lock on ClientResponseTransportImpl that thread 13 is waiting on. Hence, it's a deadlock.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms