Search Tips   |   Advanced Search

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 we understand the impact of stopping a particular server has on your 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 we 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.

During the Application Server shutdown procecess, com.ibm.ejs.util.am._Alarm might launch new threads that cause unnecessary exceptions from varied components. For example, we might receive the following Connection Pool Manager exception:

J2CA0020E: Connection Pool Manager could not allocate a Managed Connection: 
java.lang.IllegalStateException: Internal     
Error: cannot find the PoolManager Reference. 
These exceptions might occur because an application server must shut down all of the components under that application server's 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..


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 > Server Types > WebSphere application servers.

What to do next

If you experience any problems shutting down a server, see Troubleshoot administration.

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

    (Windows) (Linux) WASService command

  • Use command-line tools
  • stopServer command
  • startServer command