WAS v8.5 > Set up the application serving environment > Administer application servers > Manage application servers

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 your ability to handle work requests, especially if you need to maintain a highly available environment.

There are times you need to stop an application server. For example, you 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.

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, you 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. gotcha

• We can use the Start menu to stop the application server. In the dmgr console, click Start > Programs > IBM WebSphere > Express vn > Stop the server. When 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.

• If a Windows service has been created for the application server, optionally use the Windows Services utility to start, stop, and monitor the basic status of the server.
  1. To launch the Services utility, click Start > Settings Control Panel.

     The Control Panel folder displays.

  2. Double-click the Administrative Tools icon.

     The Administrative tools folder displays.

  3. Double-click the Services icon.

     Read about the Services utility in the Windows online help.

  Read the topic about the WASService command for information about adding and removing Windows services.

• For distributed platforms, except AIX , we can use the stopServer command to stop an application server from the command line.

  A warning message displays if you are stopping the application server that is running the dmgr console application.

  We can issue the stopServer or the stopManager commands from the /usr/WebSphere/AppServer/bin directory:

  # ./stopServer.sh server1
  # ./stopManager.sh

Results

The specified server stops as soon as requests assigned to that server finish processing. To verify the server is in stop state, in the dmgr console, click Servers > Server Types > WebSphere application servers.

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

Related

Start an application server
Manage application servers
Administer application servers

WASService command
txml_command.html

Reference:

stopServer command
startServer command

+

Search Tips   |   Advanced Search