Technical data

Lifecycle Commands
Configuring and Managing WebLogic Server 6-11
Note: Graceful Shutdown Timeout is a different attribute from
ServerLifeCycleTimeoutVal, which applies only to a force shutdown.
In-Flight Work Processing
The following sections describe how each subsystem handles work in process when it
suspends itself during a graceful shutdown.
RMI Subsystem
The RMI subsystem suspends in three steps. Each step in this process completes before
the following step commences.
1. Non-transaction remote requests are rejected by the Non-Transaction RMI Service.
2. The Client Initiated Transaction Service waits for pending client transactions to
complete.
3. The Remote RMI Service rejects all remote requests with or without transactions.
After these steps are completed, no remote client requests are allowed. Requests with
administrative privileges and internal system calls are accepted.
When a clustered server instance is instructed to prepare to suspend, the RMI system
refuses any in-memory replication calls, to allow other cluster members to choose new
secondaries.
Web Container
After the Web Container subsystem is instructed to prepare to suspend, it rejects new
sessions requests. Existing sessions are handled according to the persistence method:
! No persistence—Pending sessions with no persistence are allowed to complete.
! In-memory replication in a cluster—Sessions with secondary sessions are
immediately suspended. If a primary session does not have a secondary session,
the Web Contains waits until a secondary session is created, or until the session
times out, whichever occurs first.
! JDBC persistence and file persistence—The Web Container immediately
suspends sessions that are replicated in a database or file store.