When the J2EE server detects a configuration file update, the J2EE server starts monitoring the number of requests being processed, and loads the file when the processing of the requests is complete. If the file size is large, when the file passes through a network, and when there are multiple files, the processing time to copy the files might be longer. At this time, if the request processing finishes before the copying of the file is complete, the loading process starts while the file is being copied, and hence, the loading of the file might fail. To avoid this, you can consider the time taken to copy the files and set the interval for configuration file update in such a way that the loading starts after the copy operation is complete. With the interval for configuration file update, you set the time from the detection of a configuration file update to the start of monitoring for the number of requests being processed. The following figure shows the interval for configuration file update.

Figure 13-12 interval for configuration file update

Hint

• We recommend that you set the interval for configuration file update considering some leeway in the actual time required for copying.
• When you update multiple files concurrently, calculate the time taken to update multiple files and then set the interval for configuration file update.

You can set the interval for configuration file update for J2EE applications, Web applications, and JSPs respectively. The relationship between the set values is as follows:

For EJB applications

The interval for updating the J2EE application configuration file (ejbserver.deploy.context.update.interval) is used.

For the servlets

The interval for updating the configuration files of the Web applications or J2EE applications is used. The priority is as follows:

1. Interval for updating the Web application configuration file (webserver.context.update.interval)
2. Interval for updating the J2EE application configuration file (ejbserver.deploy.context.update.interval)

When interval for updating the Web application configuration file is not specified, the interval for updating the J2EE application configuration file is used.

For the JSPs

The interval for updating the configuration files of the JSPs or J2EE applications is used. The priority is as follows:

1. Interval for updating the JSP configuration file (webserver.jsp.update.interval)
2. Interval for updating the J2EE application configuration file (ejbserver.deploy.context.update.interval)

When the interval for updating the JSP configuration file is not specified, the interval for updating the J2EE application configuration file is used.