uCosminexus Application Server Overview

[Contents][Index][Back][Next]

4.4.3 Stopping the execution of full garbage collection in the resource exclusion status

In JavaVM, the full garbage collection is executed when the free memory size becomes less than the fixed size. When the full garbage collection is executed, all the processes on that JavaVM are interrupted. If the full garbage collection is executed while the application on the batch server is using the resources in the exclusion status, the process is interrupted as is in the exclusion status. In this case, execution of the online processes that need to use the same resources is also interrupted.

With the execution environment for batch applications, you can control the timing for executing the full garbage collection on the batch server. With this control, you can execute the full garbage collection exactly when the resources are not excluded, and can release the objects that are not required. This enables you to suppress the execution of the full garbage collection at an unintended timing.

The following figure shows an overview of controlling the full garbage collection on the batch server.

Figure 4-15 Overview of controlling the full garbage collection on the batch server

[Figure]

With the control of full garbage collection, the event that the used memory space has exceeded the threshold value is reported as shown in step 1 in the figure. After it is confirmed that the used resources are released on the batch server as shown in step 2, full garbage collection is executed as shown in step 3.