Stop an instance (stop)
- Last Updated: March 30, 2020
- 2 minute read
- OpenEdge
- Version 12.2
- Documentation
Purpose
Stop a running instance, either gracefully or forcibly.
On UNIX platforms stopping the running server instance is accomplished by sending a UNIX signal to the PAS process. Therefore, the administrator's process must have the UNIX permissions to signal the PAS process. On Windows platforms, the instance is identified using an OS process id that is used to stop server processes.
Syntax
|
Parameters
- general_options
- Specify one or more of the general TCMAN options. Run
tcman.sh help stopto see which general options are appropriate. - -F
- Kill the sever process if it does not stop after a default wait time (5
seconds on UNIX, 10 seconds on Windows). Change the default wait interval by
using the
–woption. - -w seconds
- Optionally specify the number of seconds to wait before killing a server process.
Example
Stop the server in /psc/acme1, which is an instance of the core server in /psc/pashome:
|
Notes
- TCMAN supports stopping a server instance that is not configured with a shutdown
port.
On UNIX platforms stopping the running server instance is accomplished by sending a UNIX signal to the PAS process. Therefore, the administrator's process must have the UNIX permissions to signal the PAS process. On Windows platforms, the instance is identified using an OS process id that is used to stop server processes.
The following is an example a message you would see after a forced shut down with no shut down port:
Sep 23, 2013 4:10:47 PM org.apache.catalina.startup.Catalina stopServer SEVERE: No shutdown port configured. Shut down server through OS signal. Server not shut down. Killing Tomcat with the PID: 14230 -
Process ids are stored in the following locations:
OS PID File Path UNIX $CATALINA_BASE/temp/catalina-instance_name.pid Windows $CATALINA_BASE\logs\catalina-instance_name.pid -
You can also obtain the process id of a server by running the TCMAN
envaction.