JCS WebLogic Server Automatically Shutdown and Restarted
(Doc ID 2434383.1)
Last updated on AUGUST 16, 2018
Applies to:Java Cloud Service - Version 14.1 to 14.1
Information in this document applies to any platform.
WebLogic managed server automatically shutdown and restarted
<Jul 30, 2018 9:39:50 AM AST> <Error> <> <BEA-000000> <cannot dump threads on this VM:java.version='1.7.0_171'os.name='linux' java.vendor.url='http://java.oracle.com/'
<Jul 30, 2018 9:39:50 AM AST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jul 30, 2018 9:39:50 AM AST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '57' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "616" seconds working on the request "Workmanager: default, Version: 0, Scheduled=true, Started=true, Started time: 616308 ms
or similar to below:
<BEA-310006> <Critical subsystem Thread Pool has failed. Setting server state to FAILED.
Reason: Server failed as the number of stuck threads has exceeded the max limit of 25>
<BEA-000337> <[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "606" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@4fc356e4[POST /ebiz/faces/ModulePage.jspx]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
<BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!