Monitoring policy settings
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 > Process Definition > process
type > Monitoring Policy.
Configuration tab
-
Maximum Startup Attempts
- Specifies the maximum number of times to attempt to start the
application server before giving up.
-
Ping Interval
- Specifies 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.
-
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 |
-
Automatic Restart
- Specifies whether the process should restart automatically if it
fails. The default is to restart the process automatically.
| Data type |
Boolean |
| Default |
true |
-
Node Restart State
- Specifies the desired state for the process after the node completely
shuts down and restarts.
| 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. |