Table of Contents Previous Section
The platforms on which WebObjects can be installed have various means for monitoring running processes, including WebObjects application processes, and for terminating those processes (called rather violently, on UNIX platforms, "killing" processes). There can be many reasons for terminating processes, such as to upgrade to a modified version of an application or to debug a scripted application when page-recreation is turned off.
Using a shell program (such as the Terminal application on Mach) enter the ps command on the command line. This command, without any arguments, lists minimal information about running processes. To narrow the search for a particular WebObjects application, give the following compound piped command on Solaris and HPUX:
ps -eaf | grep
ApplicationName
On Mach, the ps argumentsare different:
ps -auxwww | grep
ApplicationName
If you want to check on a scripted application, use WODefaultApp as ApplicationName. Here's some sample output:
nobody 3012 0.0 11.7 5.49M 2.81M co S 0:13 WODefaultApp -d
/NextLibrary/WebServer/htdocs Examples/TimeOff
Note that the command-line arguments are shown, thereby allowing you to learn, in the case of WODefaultApp, which scripted applications are running.
To terminate an application, note its process ID (PID) number (3012 in the above example) and "kill" it:
kill 3012
If you cannot kill the application from your own account, enter su, log into the superuser account, and try the kill command again.
On Windows NT 4.0 use the Task Manager program to monitor and terminate processes.
On Windows NT 3.51, use Visual C++'s Pview program (if installed) to terminate processes.
If you cannot terminate an autostarted application on Windows NT, it is probably because it is started under an account for which you don't have privileges. See "Autostarting Applications" for instructions on rectifying this situation.