cjreloadapp (reload application)
- Organization of this page
Format
cjreloadapp [server-name] [-nameserver provider-URL] -name application-name [-t timeout-time-until-forced-reload-starts]
Function
This command replaces the component classes and JSPs of an application without stopping the application.
For details on the session information inherited by an application after replacement, see 15.8.8 Reloading Web applications in the uCosminexus Application Server Common Container Functionality Guide.
This command can be executed only for an application that uses an exploded archive and either is running or is stopped after a reload failure.
When you execute this command, you must specify the ejbserver.deploy.context.reload_scope property in the usrconf.properties user properties file of the J2EE server. For details on the user properties file (usrconf.properties), see 2.2.3 usrconf.properties (User property file for J2EE servers) in the uCosminexus Application Server Definition Reference Guide.
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 application-name
-
Specifies the application name.
- -t timeout-time-until-forced-reload-starts
-
Specifies the maximum amount of time (in seconds) from when the command is executed to wait for forced reloading to start, as an integer in the range 0 to 2147483647.
When 0 is specified, no response is returned to the client until replacement of the component classes and JSPs has been completed. If no wait time until forced reloading starts is specified, forced reloading will not be executed.
Input examples
cjreloadapp MyServer -name App1
Return values
- 0:
-
The command terminated normally.
- 1:
-
The command terminated abnormally.
- 2:
-
The command cannot be executed because of an exclusion error.
- 3:
-
A timeout error occurred.
- 4:
-
Locking failed.
- 9:
-
The command could not be executed because there are no administrator privileges (in Windows).
Notes
-
When you specify a server name in the command arguments, you must specify it immediately after the command name. You can specify the other arguments in any order as long as they are subsequent to the server name (or subsequent to the command name if the server name is omitted). However, you cannot switch the sequence of an option name and its corresponding value (for example, you cannot specify application-name -name); also, you cannot specify an option name in conjunction with a non-corresponding value (for example, you cannot specify -nameserver application-name -name provider-URL).
-
When you specify a server name in the command arguments, you must specify a case-sensitive character string that matches a server name specified in a cjsetup (set up or unsetup J2EE server).
-
If the stop processing of J2EE application does not terminate within the time specified in -t option, the J2EE application is terminated forcibly within the time specified in ejbserver.rmi.request.timeout key of system property file for server management commands.
-
If the J2EE application contains cosminexus.xml, the definition information of cosminexus.xml is not read.