13.8.2 Scope of reloading

The following table describes the types of applications that can be specified for reloading.

Table 13-9 Types of applications that can be specified for reloading

Types of applicationsApplicabilityRestrictions
EJB application (EJB-JAR)Stateless Session BeanRA new request during the reload process results in an error. Note that if the CTM is used, a new request during the reload process is added to the pending list.
Stateful Session BeanRA new request during the reload process results in an error. Also, if reloaded, the application state is destroyed, so the application state returns to the state before the application was started.
Singleton Session BeanRIf reloaded, the Bean instance is destroyed, and an instance is re-created, so the state of the instance is not stored.
Entity BeanRA new request during the reload process results in an error.
Message-driven BeanR
Web application (WAR)ServletY--
JSPY--
Library JAR--Y--
Legend:
Y: Can be specified for reloading.
R: Can be specified for reloading, there are restrictions
--: Not applicable

You can specify the scope of reloading with the following range:

Note: app, web, jsp are the values specified in the ejbserver.deploy.context.reload_scope key of usrconf.properties. Note that if you specify none, the reload functionality is disabled.

When app is specified
  • If you update an EJB application, the EJB application, servlets, and JSPs are reloaded.
  • If you update a servlet, the servlets and JSPs are reloaded.
  • If you update a JSP, the JSP is reloaded.
When web is specified
  • If you update a servlet, the servlets and JSPs are reloaded and if you update a JSP, the JSP is reloaded.
  • If the servlets exist and the JSPs do not exist, only the servlets are reloaded. If the JSPs exist and the servlets do not exist, only the JSPs are reloaded.
  • Reloading is not performed even if you update the EJB application.
When jsp is specified
  • If you update a JSP, the JSP is reloaded.
  • Reloading is not performed even if you update the EJB application or servlet.

Note that enabling or disabling of the reload functionality is decided based upon the combination of the scope of the local call optimization functionality specified in the ejbserver.rmi.localinvocation.scope key of usrconf.properties and scope of the reload functionality. The following table describes the mapping of the scope of the local call optimization functionality and the scope of the reload functionality.

Table 13-10 Mapping of the scope of the local call optimization functionality and the scope of the reload functionality

ItemsValue of the ejbserver.rmi.localinvocation.scope key
allappnone
Scope of local call optimizationWithin the same J2EE server.Within the same application.There is no range.
Value of the ejbserver.deploy.context.reload_scope keyappN#YY
webYYY
jspYYY
noneNNN
Legend:
Y: Reload functionality can be used
N: Reload functionality cannot be used

#: The settings are incorrect. If you specify ejbserver.deploy.context.reload_scope=app for ejbserver.rmi.localinvocation.scope=all, a message is output when you start the J2EE server and the server fails to start.