WebLogic Stuck Threads
Posted by Ben Collins on 12 September 2018 12:58 PM
Hyperion Essbase - Version and later
Information in this document applies to any platform.
***Checked for relevance on 12-May-2014***


The following error msg is displayed many times during different dates: "which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:"

Provider services is frequently going down hitting the following error:

<WLS Kernel>> <> <> <1289932400273> <BEA-000337> <[STUCK] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "651" seconds working on the request "Http Request: /aps/APS", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace


Environments need to be tuned when reaching the default setting limits interacting with Web Logic.


In Essbase Administration Services use the default Stuck Threads settings as a starting point.
Then after careful testing of your long running transaction, adjust as needed.

Stuck Thread Max Time=600 ( Default Value)
Stuck Thread Max Time=1200 ( Suggested Value)

To modify the "Stuck Threads" setting:

1. Login to the Weblogic Admin Server Console.
2. Navigate to Domain Structure -> Servers.
3. Select EssbaseAdminServices0 (or the sever you want to modify).
4. On the Tuning Tab, select to "Lock & Edit".
5. Modify the setting "Stuck Thread Max Time" and "Save".

For more information on this setting, refer to KM Document "What Does a Stuck Thread Mean in WebLogic Server? (Doc ID 1287878.1)".

(0 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: