Try OpenEdge Now
skip to main content
Servers, DataServers, Messengers, and Adapters
Managing WebSpeed Transaction Server Data : Modifying WebSpeed control settings : Killing a WebSpeed agent process
 

Killing a WebSpeed agent process

You might want to manually terminate an agent process under these two circumstances:
*An agent process hangs.
*You determine from the available data that an agent process is a runaway process.
The specific PID on the Agent pool summary section of the Agent Pool Control page allows you to access the necessary page to kill the offending agent's process.
When either of the previously listed circumstances exists and you want to manually terminate an agent process, use this command:
kill -9
Caution: An agent (or server) process that has database locks can cause a database crash when you kill the process using the kill -9 command. Therefore, use the command 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 that 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 a process.
You can also kill an AppServer process. For details, see Killing an AppServer process .
To initiate a kill process:
1. Click the PID associated with the agent process you want to terminate. The specific WebSpeed Broker PID page appears, as shown:
Note that the two sections on this page present relevant summary information about this WebSpeed agent and its current operational status. See Viewing broker process details for details about this data.
2. Click Kill to terminate this process. (Alternatively, you can click Cancel at the top of the page to exit the page without terminating the process.)
OpenEdge Management will prompt you once again to verify you want to terminate this process. Click OK.
A final status page appears that identifies the status of your kill request and displays one of the following messages:
*Process xxxxx has been terminated — This message indicates that the process was successfully killed. The PID number previously associated with this process is now available for the operating system to reassign.
*Process xxxxx cannot be killed at this time — This message indicates that the process could not be killed. In very rare instances, it is possible that you will not be successful in an attempt to kill a process. You can retry the kill process procedure; however, it is possible that the process will persist for a number of unknown reasons.
*Process xxxxx has been reused — OpenEdge Management has determined that the process PID number and associated time and date stamp do not match the values that the operating system has stored for this same process. Consequently, when you click Kill, the process cannot be destroyed.