Stopping an application server

Stopping an application server ends a server process based on the process definition settings in the current application server configuration.

Make sure you understand the impact of stopping a particular server has on the ability to handle work requests, especially if we need to maintain a highly available environment.

There are times we need to stop an application server. For example, we might have to apply service to an application running on that server, or you might want to change one of the application server's configuration setting. Use one of the following options when we need to stop an application server.

Avoid trouble: During the Application Server shutdown procecess, might launch new threads that cause unnecessary exceptions from varied components. For example, you might receive the following Connection Pool Manager exception:

These exceptions might occur because an application server must shut down all of the components under that application servers control before the stop process can complete. We can ignore these exceptions. After the application server stops, all running threads from the application server automatically end. gotcha


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 console, click Servers > Server Types > WebSphere application servers.

What to do next

If we experience any problems shutting down a server, see Troubleshooting administration.

Related tasks

  • Start an application server
  • Manage application servers
  • Administer application servers
  • Create application servers

  • WASService command
  • txml_command.html

  • stopServer command
  • startServer command