7.3.5 stop
This subcommand stops the specified logical servers, J2EE application, or J2EE resources.
The following table shows the arguments that can be specified for the stop subcommand.
|
Argument |
Explanation |
Target specification |
|
|---|---|---|---|
|
Logical server |
Host |
||
|
allServers |
Stops the logical servers defined in the management domain in reverse order from the defined starting order. |
-- |
-- |
|
server [graceful[:waitTime]] |
Stops the logical server specified by the -t option. When graceful is specified, planned termination is executed. |
Y |
Y |
|
app displayName [force] |
Stops the J2EE application specified by displayName that has been started on the logical server specified by the -t option.# When force is specified, the application is stopped forcibly. |
Y |
-- |
|
resAdapter displayName |
Stops the J2EE resource adapter specified by displayName that has been started on the logical server specified by the -t option.# |
Y |
-- |
|
resJavaBeans displayName |
Stops the JavaBeans resource specified by displayName that has been started on the logical server specified by the -t option.# |
Y |
-- |
- Legend:
-
Y: Can be specified.
--: Cannot be specified.
- #
-
displayName indicates the display name of a J2EE application, J2EE resource, or JavaBeans resource.
You can use the stop subcommand to execute the following two types of operations:
-
Specify the allServers argument to stop the specified logical servers.
Stops the logical servers defined in the management domain in reverse order from the defined starting order. When server is specified for the argument, the subcommand stops the logical server specified by the -t option (smart agent, naming service, J2EE server, J2EE server cluster, CTM, CTM domain manager, performance tracer, Web server, Web server cluster, or user server).
When server is specified for the first argument, you can specify graceful for the second argument. When graceful is specified and the logical server specified by the -t option is a Web server or Web server cluster, planned termination is applied to the logical server. Planned termination means that the logical server is stopped only after all requests that have been accepted have been processed. If the logical server specified by the -t option is not a Web server or Web server cluster, or if a host name is specified for the -t option, the graceful argument is ignored. You can also specify with the graceful argument a waitTime to set a maximum amount of time (in seconds) to wait for the stop to occur. Specify a value between 60 and 1,800 seconds for waitTime. If the request has not terminated by the time the specified amount of wait time has elapsed, the logical server is terminated forcibly. If :waitTime is omitted, the stop monitoring time specified in the mstartup.watchtime parameter of the Smart Composer functionality is setup.
-
Specify two arguments for the stop subcommand to stop the specified J2EE application, J2EE resource adapter, or JavaBeans resource.
When app, resAdapter, or resJavaBeans is specified for the first argument, the subcommand stops the J2EE application, resource adapter, or JavaBeans resource that is specified by displayName (the second argument) and has been started on the J2EE server specified by the -t option. In the case of a J2EE server cluster, the operation is expanded to its member J2EE servers.
If a logical server that is not a J2EE server (including a J2EE server cluster member) or that is not a J2EE server cluster is specified by the -t option, an error occurs. A host name cannot be specified by the -t option.
When app is specified for the first argument, you can specify force for the third argument. When the force argument is specified, the logical server is terminated forcibly without waiting for it to complete its processing even if the J2EE application is executing a request.
A J2EE application that has been started in the test mode cannot be stopped.
- Notes
-
-
If execution of the start or stop subcommand is immediately followed by a similar operation on the same logical server, specify the -s option in the subcommand so that the subsequent command is executed after completion of the subcommand.
-
If the list subcommand is specified, the status existing when the subcommand is invoked is reflected in the information that the command returns, regardless of the execution states of other subcommands (such as start and stop). Therefore, the command might return the status working before the processing of the start subcommand is completed or the status stopped before the processing of the stop subcommand is completed.
-
Of the logical servers to be stopped, the ones placed in abnormal ended status are assumed to have already been stopped. Attempts are not made to retry the subcommand to stop these logical servers. In 09-70 and earlier versions, however, attempts are made to retry the subcommand. In this case, when stop processing is performed for a logical server abnormal ended status, the subcommand waits until the maximum monitoring time expires and then terminates with the return value 1. The maximum monitoring time is specified in the -l option and its default value is 60 seconds.
-
If you want to stop the logical CTM server that is set in the CTM to which a logical J2EE server is connected, stop the logical J2EE server first. After you confirm that the processing to stop the logical J2EE server is complete, stop the logical CTM server. If you attempt to stop the logical CTM server before the processing to stop the logical J2EE server is complete, the attempt might fail. You can check whether the processing to stop the logical J2EE server is complete from whether the J2EE server process (cjstartsv) has stopped.
-