Technical data

6 Server Lifecycle
6-4 Configuring and Managing WebLogic Server
Understanding Server State
The following sections describe the key states that a server instance can have, the
processing associated with the state, and how the state fits into a sequence of state
transitions.
SHUTDOWN
In the SHUTDOWN state, a server instance is configured but inactive. A server instance
reaches the
SHUTDOWN state as a result of a graceful shutdown or forced shutdown.
A graceful shutdown can be initiated when the server instance is in the
RUNNING or the
STANDBY state. The graceful shutdown process consists of the following state
transitions:
RUNNING→SUSPENDING→STANDBY→SHUTTING DOWN→SHUTDOWN
For more information about the graceful shutdown process, see “Graceful Shutdown”
on page 6-9.
A forced shutdown can be initiated from any server state. The forced shutdown process
consists of the following state transitions:
any state→STANDBY→SHUTTING DOWN→SHUTDOWN
For more information about the forced shutdown process, see “Forced Shutdown” on
page 6-13.
For information about issuing stop commands, see “Starting and Stopping Servers” in
Administration Console Online Help.
STARTING
In the STARTING state, a server instance prepares itself to accept requests and perform
application processing. A server instance cannot accept requests while in the
STARTING state.
When a server instance starts itself, it retrieves its configuration data, starts its
kernel-level services, initializes subsystem-level services, deploys applications, and
loads and runs startup classes. For more information about the startup process, see
“Start” on page 6-8.