How to Set Timeout on Force Shutdown of WebLogic Managed Server
(Doc ID 1272037.1)
Last updated on OCTOBER 04, 2021
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
A force shutdown operation shuts down WebLogic Server without delay, ignoring work in process. All server services are halted. External resources such as connection pools and file stores are closed.
Usually a force shutdown will execute quickly and will not block. However, WebLogic will invoke application code during a force shutdown, such as in Servlet
ejbRemove(). Since applications may need access to JMS, JDBC, and transaction services during shutdown, WebLogic shuts down applications first, and then stops JMS, JDBC, and transactions later. Thus, a force shutdown can be delayed by application processing. Also, a force shutdown can fail, and throw a ServerLifecycleException. After a shutdown failure, the server will exit only after the number of seconds specified by the
When running WebLogic in development mode, a force shutdown operation waits 30 seconds by default before timing out. Similarly, when running WebLogic in production mode, a force shutdown operation waits 120 seconds by default before timing out. The longer default timeout for production mode gives applications more time to exit. A timeout setting of zero means the server will wait indefinitely for the force shutdown to complete.
When the force shutdown times out, WebLogic forcibly terminates the currently running Java virtual machine. Although the default values for
ServerLifecycleTimeoutVal will be enough for most applications, it is possible that application processing may require that you increase the amount of time WebLogic waits for a force shutdown. If so, you can adjust the timeout value on a WebLogic Server force shutdown rather than use the default values.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document