cjstopapp (stop J2EE application)

Format

For executing a normal termination

cjstopapp [server-name] [-nameserver provider-URL]
    -name J2EE-application-name [-t timeout-time]

For manually executing a forced termination after a normal termination times out

cjstopapp [server-name] [-nameserver provider-URL]
    -name J2EE-application-name -cancel

For automatically executing a forced termination after a normal termination times out

cjstopapp [server-name] [-nameserver provider-URL]
    -name J2EE-application-name -t timeout-time -force

Function

This command stops a J2EE application and disables it from receiving requests from clients.

Arguments

server-name
Specifies the name of a connected J2EE server. If the server name is omitted, the host name is assumed.
-nameserver provider-URL
Specifies the access protocol for the CORBA Naming Service, the name of the host running the CORBA Naming Service, and the port number being used by the host. These items are specified in the following format:

protocol-name: : host-name: port-number

For details on the specification items, see 2.1(2) Provider URL.
-name J2EE-application-name
Specifies the name of the J2EE application that is to be stopped.
-t timeout-time
Specifies the maximum amount of time (in seconds) from when the command is executed to wait for a response to be returned, as an integer in the range 0 to 2147483647. When 0 is specified, no response is returned to the client until stop processing is completed. If this argument is not specified, a time of 60 seconds is assumed.
-cancel
Specifies that the J2EE application is to be forcibly terminated manually after a normal termination times out.
-force
Specifies that the J2EE application is to be forcibly terminated automatically after a normal termination times out.

Input examples

cjstopapp MyServer -name App1

Return values

0:
The command terminated normally.
1:
The command terminated abnormally.
2:
The command could not be executed because of an exclusion error.
3:
A timeout occurred.
9:
The command could not be executed because there are no administrator privileges (in Windows Server 2012, Windows Server 2008, Windows 8, Windows 7, or Windows Vista).

Notes