Search Tips   |   Advanced Search

stopServer command

The stopServer command reads the configuration file for the specified server process. This command sends a Java management extensions (JMX) command to the server telling it to shut down.

The server process can be an application server, a DMZ Secure Proxy Server for IBM WebSphere Application Server, an administrative agent server, or a job manager server

By default, the stopServer command does not return control to the command line until the server completes the shutdown process. There is a -nowait option to return immediately, and other options to control the behavior of the stopServer command. For more information about where to run this command, see the Use command-line tools topic.

(Dist) If we are running the product on a Microsoft Windows operating system, and we have the server running as a Windows operating system service, the stopServer command stops the Windows service that is responsible for starting the server.

(iSeries) Although the stopServer command returns control when the server completes shut down, it can return before the IBM i process has terminated. Depending upon the amount of memory which the JVM must return to the memory pool, the process may take several seconds or minutes to completely end. We should not attempt to start the server again until the process has terminated. Use the WRKACTJOB SBS(subsystem) CL command to determine if the process has terminated completely. By default, the subsystem is QWAS85.

(AIX) (Linux) (Solaris) (HPUX) If security is enabled, we must use a user name and password with the stopServer command because the command invokes an MBean method on the server.

(Windows) The user name and password parameters are not required with the stopServer command. The parameters are automatically passed into the script that the Windows operating system service uses to shutdown the system.

If message ADMC0074E: Connection will be closed due to unrecoverable error is displayed in the system log file, a client might have attempted to send a user name, and password to another server on which security is disabled. We can ignore this message because the client automatically changes its security setting to match the security setting for the server with which the client is trying to communicate. The connection is eventually successfully completed. However, security is now disabled for both the administrative client and the receiving server.


The command syntax is one of the following:

where server_name is the name of the configuration directory of the application server or the DMZ Secure Proxy Server for IBM WAS to stop.

This argument is required.

(iSeries) This argument is optional. If the default profile is being used, the server defaults to server1. If the profile name is not default, the server defaults to the profile name.

whereadminagent_name is the name of the administrative agent to stop.

where job_manager is the name of job manager to stop.


The following options are available for the stopServer command:


Tells the stopServer command not to wait for successful shutdown of the server process.


Suppresses the progress information that the stopServer command prints in normal mode.

-logfile <fileName>

Location of the log file to which trace information is written. By default, the log file is named stopServer.log and is created in the logs directory.


Define the profile of the server process in a multi-profile installation. The -profileName option is not required for running in a single profile environment. The default for this option is the default profile.


Replace the log file instead of appending to the current log.


Generate trace information into a file for debugging purposes. The trace output is written to the stopServer.log file which is located in the profile_root/logs/server directory.

-timeout <seconds>

Time to wait for server shutdown before timing out and returning an error.

-statusport <portNumber>

An optional parameter that allows an administrator to set the port number for server status callback. The tool opens this port and waits for status callback from the server just before the server has stopped. If the parameter is not set, an unused port is automatically allocated.

-conntype <type>

The JMX connector type to use for connecting to the deployment manager. Valid types are SOAP or Remote Method Invocation (RMI).

-port <portNumber>

Server JMX port to use explicitly, so that we can avoid reading the configuration files to obtain the information.

-username <name>

User name for authentication if security is enabled in the server. Acts the same as the -user option.

-user <name>

User name for authentication if security is enabled in the server. Acts the same as the -username option.

-password <password>

Password for authentication if security is enabled in the server.

If we are running in a secure environment but have not provided a user ID and password, we receive the following error message:

    ADMN0022E: Access denied for the stop operation on Server MBean due to insufficient or empty credentials.

To solve this problem, provide the user ID and password information.


Print a usage statement.


Print a usage statement.

Usage scenario

The following examples demonstrate correct syntax:


  • Use command-line tools