Weblogic Server Hung Caused By Stuck Threads Due To Using Third-Party Component OSCACHE

(Doc ID 1381812.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version: 10.0 and later   [Release: and later ]
Information in this document applies to any platform.


WebLogic Server hung, and we found the following stuck thread in the thread dump:

<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '162' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "612" seconds working on the request "Http Request: /chinalfWeb//InnerIndexShowCol", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-197815 "[STUCK] ExecuteThread: '162' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, waiting, priority=1, DAEMON> {
-- Waiting for notification on: com.opensymphony.oscache.base.EntryUpdateState@898a45c[fat lock]
jrockit.vm.Threads.waitForSignal(Native Method)
jrockit.vm.Locks.wait(Unknown Source)
jrockit.vm.Locks.wait(Unknown Source)


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