The following table describes the operations to be performed when an error occurs while the reload functionality is being used.
Table 13-12 Operations when an error occurs in the reload functionality
Error contents | Results |
---|---|
When a request arrives in the server during reloading (state when no request is being processed in the application) | For the EJB-JARs, an error is returned to the client. For the WARs, the new request remains pending until the reloading is finished. |
When an exception occurs during reloading (including failure in the loading of the class file) | The application is stopped without stopping the update detection process. When an update is detected, the stopped J2EE application is restarted. |
When an exception occurs in processing other than reloading (during update check, during the interval for updating configuration file, during delayed reloading) | The monitoring continues with the J2EE application running and without stopping the update detection process. |
When a J2EE application method does not terminate because it has hung up | Reload cannot be executed unless you cancel the method for monitoring the J2EE application execution time. Also, reload cannot be executed unless you use the cjreloadapp command. For details on the monitoring of the J2EE application execution time, see 13.8.10(2) Relationship between reloading and monitoring the J2EE application execution time. |