Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Monitor policy settings
Use this page to view or change settings that control how the node agent monitors and restarts a process. From the console...
Servers > Server Types > WebSphere application servers > server_name
Then, under Server Infrastructure, click Java and process management > Monitoring policy.
Maximum Startup Attempts
Maximum number of times the product tries to start an application server in response to a start request. If the server cannot be started within the specified number of attempts, an error message is issued that indicates that the application server could not be started.
Data type Integer Default 3
Ping Interval
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. Default 60
- If you set this property to 0. which indicates that no checking is performed, certain threads, such as PidWaiter, might terminate before the threads return their status to the initiating thread. In these situations, the dmgr might not notifying the node agents of certain events, which could negatively impact stopServer.sh processing.
- If you set this property to a value greater than 0 but less than or equal to 5, the actual value used for the Ping Interval is 5.
Ping Timeout
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. Default 300
Automatic Restart
Whether the process should restart automatically if it fails.
If you change the value specified for this field, 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 true for the distributed and IBM i environments
Node Restart State
The setting only displays for the WAS ND. It specifies the desired behavior of the servers after the node completely shuts down and restarts.
If a server is already running when the node agent stops, that server is still running after the node agent restarts. If a server is stopped when the node agent restarts, whether the node agent starts the server depends on the setting for this property:
- If this property is set to STOPPED, node agent does not start the server.
- If this property is set to RUNNING, the node agent always starts the server.
- If this property is set to PREVIOUS, the node agent starts the server only if the server was running when the node agent stopped.
Changes you make to the node restart state become effective after the node is synchronized. At the next NodeAgent restart (after the synch), the node restart state will be honored.
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.
Define application server processes