Stop an appserver
Overview
Stopping an appserver ends a server process based on the process definition settings in the current appserver configuration.
Make sure you understand the impact of stopping a particular server has on your ability to handle work requests, especially if maintain a highly available environment.
There are times stop an appserver. For example, you might have to apply service to an application running on that server, or you might want to change one of the appserver's configuration setting. Use one of the following options when stop an appserver.
Procedure
You can use the Start menu to stop your appserver. In the administrative console, click...
Start | Programs | IBM WebSphere | ND v.x | Stop the serverWhen the server stops successfully, the stopServer.log file contains the following in the last two lines:
Server stop request issued. Waiting for stop status. Server server1 stop completed.The server name varies depending on your settings.
- You can issue the stopServer command from the command line to stop a single server or the stopManager command to stop the deployment manager.
# cd /usr/WebSphere/AppServer/bin directory:
# ./stopServer.sh server1
# ./stopManager.sh
- You can use the administrative console to stop an appserver:
- In the console, click...
Servers | Application Servers
- Select the appserver that you want stopped and click Stop.
- Confirm to stop the appserver.
- View the Status value and any messages or logs to see whether the appserver stops.
Results
The specified server stops as soon as requests assigned to that server finish processing. To verify that the server is in stop state, in the administrative console, click...
Servers | Application Servers
What to do next
If you experience any problems shutting down a server, see Troubleshooting administration.
Application servers
Related tasks
Start an appserver
Manage appservers
Administering appservers
Creating appservers
Related Reference
stopServer command
startServer command