Killing an AppServer process
- Last Updated: October 22, 2015
- 2 minute read
- OpenEdge
- Version 13.0
- Documentation
Killing an AppServer process
You might want to manually terminate an agent process when:
- An agent process hangs
- You determine from the available data that an agent process is a runaway process
The specific PID in the Agent pool summary on the Server Pool Control page allows you to access the page to kill the offending agent's process.
Note: OpenEdge Management references
the specific PID and its associated date
and time start details to be sure of a process' identity before
it attempts to kill the process.
You can choose to kill the process in two ways:
- Kill-Terminate the process immediately
- Stop-Complete the process and then terminate it.
Because you want to manually terminate an agent process only under the two circumstances listed above, the command used when you kill the process is:
|
Note: An agent (or server) process
that has database locks can cause a database crash when you kill
the process using the kill -9 command. Use
the command, therefore, only as a last resort.
The description of the signal for the kill process is as follows:
- Signal Name — SIGKILL
- Signal Number — 9
- Signal Description — Kill program
Note: OpenEdge Management references the specific PID and
its associated date and time start details to be sure of a process'
identity before it attempts to kill the process.
You can also kill a WebSpeed agent process. For details, see Killing a WebSpeed agent process.
To initiate a kill process: