13.7.2 Statuses and replacement of J2EE applications
(1) When a running J2EE application is replaced
When a running J2EE application is replaced, the replaced J2EE application is also in the running state.
If you redeploy a running J2EE application, the replacement processing is implemented with the following procedure:
- Stop the J2EE application
- Replace the J2EE application
- Start the J2EE application
Each processing has a timeout value.
- Timeout for stopping the application
- When the execution time for stopping a J2EE application exceeds the timeout value in the server management command, the J2EE application is stopped forcefully. After the forced termination, if the J2EE application does not stop even if after the timeout value set by forced termination is exceeded, the server management command terminates abnormally.
- For details on the timeout settings, see cjreplaceapp (Replacing applications) in the uCosminexus Application Server Command Reference Guide.
- Note that the value that could be acquired first is applied to the timeout value in the following order:
- Timeout value set in the server management command
- Default value (60 seconds)
- Timeout for replacing and starting the application
- When the execution time for replacing and starting a J2EE application exceeds the time set as the timeout value for the respective processing, the server management command terminates abnormally. Note that the time set in the timeout for RMI-IIOP communication is applied to the timeout value. For details on the RMI-IIOP communication timeout, see 2.11.5 Timeout in the RMI-IIOP communication in the uCosminexus Application Server EJB Container Functionality Guide.
(2) When a stopped J2EE application is replaced
When a stopped J2EE application is replaced, the replaced J2EE application is also in the stopped state. When a stopped J2EE application is redeployed, only the replacement processing of the application is executed.