|
Administration Console Online Help
|
Server --> Control --> Start-Stop
Tasks Related Topics Operations Attributes Status
Overview
The Server—>Control—>Start/Stop tab changes the state of a server.
Some of the operations require the Node Manager and the domain-wide administration port. In addition, some operations cannot be used for an Administration Server.
Tasks
Starting Managed Servers from the Administration Console
Resuming a Server
Shutting Down a Server
Starting All Managed Servers in a Domain
Shutting Down All Servers in a Domain
Enabling the Domain-Wide Administration Port
Related Topics
Overview of Node Manager
Overview of the Server Lifecycle
Operations
The following table describes the applicability and requirements of each operation:
|
Operation
|
Description
|
Requirements/Restrictions
|
|
Start this server in standby mode
|
Starts a Managed Server but places it in the STANDBY state.
In this state, the server can accept administration commands and it can participate in cluster communication, but it is not accessible to requests from external clients.
The operation ignores the Startup Mode setting on the Servers—>Configuration—>General tab.
|
Requires the Node Manager.
Requires the administration port to be enabled.
Only available for Managed Servers.
|
|
Start this server
|
Starts a Managed Server.
The operation ignores the Startup Mode setting on the Servers—>Configuration—>General tab.
|
Requires the Node Manager.
Only available for Managed Servers.
|
|
Resume this server
|
Moves a server from the STANDBY state to RUNNING.
|
Requires the administration port to be enabled.
|
|
Shutdown this server
|
Gracefully stops a server. New requests are rejected but in-work requests are completed before the server stops.
|
|
|
Force shutdown of this server
|
Immediately stops a server. In-work requests are dropped, no new requests are accepted, and the server immediately stops.
|
|
Attributes
Table 1-10
|
Attribute Label
|
Description
|
Value Constraints
|
|
Ignore Sessions During Shutdown
|
Indicates whether a graceful shutdown operation drops all HTTP sessions immediately. If this attribute is set to false, a graceful shutdown operation waits for HTTP sessions to complete or timeout.
MBean: weblogic.management.
configuration.ServerMBean
Attribute: IgnoreSessionsDuringShutdown
|
Default: false
Valid values:
Configurable: yes
Dynamic: yes
|
|
Graceful Shutdown Timeout
|
Number of seconds a graceful shutdown operation waits before forcing a shut down. A graceful shutdown gives WebLogic Server subsystems time to complete certain application processing currently in progress. If subsystems are unable to complete processing within the number of seconds that this attribute specifies, then the server will force shutdown automatically.
A value of 0 means that the server will wait indefinitely for graceful shutdown to complete.
This attribute applies only to graceful shutdown operations, while the ServerLifeCycleTimeoutVal attribute applies only to force shutdowns.
MBean: weblogic.management.
configuration.ServerMBean
Attribute: GracefulShutdownTimeout
|
Units: seconds
Minimum: 0
Default: 0
Configurable: yes
Dynamic: yes
|
Status
Table 1-11
|
Table Column
|
Description
|
|
Name
|
The name of the current server instance.
|
|
State
|
The current lifecycle state of the server. For a description of lifecycle states, refer to Understanding Server State.
|
|
Transition Activity
|
Shows the status of the most recent transition in lifecycle state. For details on the transition, click the link in the Status tab.
|
