Use this page to view or change settings that control how the node agent monitors and restarts a process.
To view this administrative console page, click Servers > Application Servers > server_name. Then, under Server Infrastructure, click Java and Process Management > Monitoring Policy.
Specifies the maximum number of times to attempt to start the application server before giving up.
Data type | Integer |
Specifies, in seconds the frequency of communication attempts between the parent process, such as the node agent, and the process it has spawned, such as an application server. Adjust this value based on your requirements for restarting failed servers. Decreasing the value detects failures sooner; increasing the value reduces the frequency of pings, reducing system overhead.
Data type | Integer |
Range | Set the value greater than or equal to 0 (zero) and less than 2147483. If you specify a value greater than 2147483, the application server acts as though you set the value to 0. When you specify a value of 0, no checking is performed. |
In a z/OS environment, the Ping Interval setting
for a deployment manager or a node agent is ignored. However, the
Ping Interval setting for an application server is used by the node
agent to control the native z/OS operating system PidWaiter monitoring
function. PidWaiter monitoring is similar in functionality to the
pinging function that is used in a distributed platform environment.
Both of these monitoring functions determine whether an application
server is still running. The only difference between the two monitoring
functions is that PidWaiter monitoring does not send any of the TCP/IP
messages that Ping Interval monitoring sends.
When this property is set for the deployment manager, it regulates how frequently the deployment manager checks to see if the node agent is still running. When it is set for the node agent, it regulates how frequently the node agent checks to see if the deployment manager is still running. When it is set for an application server, it regulates how frequently the application server checks to see if the node agent is still running.
Adding these two properties does not completely
eliminate DNS lookups from within WebSphere Application Server processes.
When a parent process is spawning a child process, such as when a process manager spawns a server, the parent process pings the child process to see whether the child was spawned successfully. This value specifies the number of seconds that the parent process should wait (after pinging the child process) before assuming that the child process failed.
Data type | Integer |
Units | Seconds |
Range | Set the value greater than or equal to 0 (zero) and less than 2147483647. If you specify a value greater than 2147483647, the application server acts as though you set the value to 0. |
Specifies whether the process should restart automatically if it fails.
If you change the value specified for this field, you must restart the application server and the node agent before the new setting takes effect.
This setting does not affect what you specified for the Node Restart State setting. The two settings are mutually exclusive.
Data type | Boolean |
Default |
|
The setting only displays for the Network Deployment product. It specifies the desired behavior of the servers after the node completely shuts down and restarts.
This setting does not affect what you specified for the Automatic Restart setting. The two settings are mutually exclusive.
Data type | String |
Default | STOPPED |
Range | Valid values are STOPPED, RUNNING, or PREVIOUS. If you want the process to return to its current state after the node restarts, use PREVIOUS. |