5.5.3 Stop process
The stop process is implemented in the following order:
-
Stop process of the J2EE application
-
Undeploy process of the J2EE application
The following points describe each process:
- Organization of this subsection
(1) Stop process
The stop process is implemented in the following order. Note that the J2EE application cannot be executed after the process ends.
-
Processing to stop the Web application
-
Processing to stop EJB
-
Processing to stop the J2EE application
The following points describe each process:
(a) Processing to stop the Web application
The stop process of Web application is implemented in the following order:
-
Processing to end the servlet or JSP
The destroy method of servlet and the jspDestroy method of JSP is executed.
-
Destroying the HTTP session
The HTTP session attributes are deleted and disabled.
-
Processing to end the filter
The destroy method of filter is executed.
-
Destroying the servlet context
The servlet context attributes are destroyed and disabled.
-
Deleting the execution environment of the Web application from the name space
ejb-ref, ejb-local-ref, resource-ref, env-entity, etc., are deleted from the name space.
(b) Processing to stop EJB
The stop process of EJB is implemented in the following order:
-
Deleting the execution environment of EJB from the name space
ejb-ref, ejb-local-ref, resource-ref, env-entity, etc., are deleted from the name space.
-
Deleting the EJB home object or the EJB local home object from the name space
The EJB home object or the EJB local home object is deleted from the name space.
-
Deleting the pool
The method-ready pool is deleted in the case of Session Bean and Message-driven Bean.
The pool and ready pool are deleted in the case of Entity Beans.
(c) Processing to stop the J2EE application
The entries of the J2EE application are deleted from the name space in the stop process of the J2EE application.
(2) Un-deploy process
The un-deploy process is implemented in the following order. Note that the J2EE application is deleted from the J2EE server after the process ends.
-
Processing to un-deploy the Web application
-
Processing to un-deploy EJB
-
Processing to un-deploy the J2EE application
The following points describe each process:
(a) Processing to un-deploy the Web application
Java source files and class files that are the JSP compilation results are deleted during the un-deploy process of the Web application. For JSP compilation results, see 2.5.6 JSP compilation results when JSP pre-compile is not used in the uCosminexus Application Server Web Container Functionality Guide.
(b) Processing to un-deploy EJB
The un-deploy process of EJB is implemented in the following order:
-
Deleting the remote adapter (only when the remote interface is supported)
-
Deleting the table created when CMR is used
(c) Processing to un-deploy the J2EE application
The files downloaded manually by the user are deleted in the un-deploy process of the J2EE application.