Technical data

6 Server Lifecycle
6-10 Configuring and Managing WebLogic Server
Graceful Shutdown Sequence
The following list shows the order in which subsystems suspend themselves. Each
subsystem completes its in-flight work before the next one commences its preparation
to suspend.
1. Non-Transaction RMI Service
2. Web Container
3. Client Initiated Transaction Service
4. Remote RMI Service
5. Timer Service
6. Application Service
7. EJB Container
8. JMS Provider
9. JDBC Container
10. Transaction Service
Controlling Graceful Shutdown
ServerMBean has two new attributes for controlling the length of the graceful
shutdown process. Their values are displayed and configurable on the
Server
→Control→Start/Stop tab:
! Ignore Sessions During Shutdown— If you enable this option WebLogic Server
will drop all HTTP sessions immediately, rather than waiting for them to
complete or timeout. Waiting for abandoned sessions to timeout can significantly
lengthen the graceful shutdown process, because the default session timeout is
one hour.
! Graceful Shutdown Timeout—Specifies a time limit for a server instance to
complete a graceful shutdown. If you supply a timeout value, and the server
instance does not complete a graceful shutdown within that period, WebLogic
Server will perform a forced shutdown on the server instance.