4.2 Overview of resource depletion monitoring functionality
This section describes how to monitor resource depletion on the J2EE server based on the changes in resource usage percentage or quantity.
You can use the resource depletion monitoring functionality to monitor seven types of resources. You can monitor all resources, or select the resources for monitoring. In the resource depletion monitoring functionality, specify the resources to be monitored and the threshold values for each resource. The resources of the J2EE server or batch server are subject to resource depletion monitoring.
If resource depletion monitoring for the J2EE server or batch server is enabled, information about monitoring-target resources is periodically output to a file. This information is called resource depletion monitoring information. You can choose whether to output the resource depletion monitoring information for each type of resource to be monitored. The file to which the resource depletion monitoring information is output is called resource depletion monitoring log file.
When the resource depletion monitoring information is used, you can check how the usage rate of resources or the number of resources used change. Moreover, this information can also be used to investigate the reason due to which the usage rate of resources or the number of used resources exceeds the threshold value.
An alert occurs when the threshold value specified for the usage rate of resources or the number of used resources is exceeded. If an alert occurs when using the Management Server, you can output a message and notify an event to the Management Server. This event is called a Management event. At the Management Server side, you can define the operation to be executed when a management event is notified, so that an action can be automatically executed when the management event occurs. This action is called a Management action. You can combine and use the resource depletion monitoring functionality and the Management event to monitor the resources effectively and reliably. For details on the management events and management actions, see the section 9.3 Controlling the Execution of Management Action.
For details on setting the automatic execution of processes with Management events, see the section 9.4 Settings for automatic execution of processes by management events.
For output destination of the resource depletion monitoring log file, see 4.3.1 Acquiring the Cosminexus Component Container Logs in the uCosminexus Application Server Maintenance and Migration Guide.
For settings for monitoring the resource depletion, see 4.3.3 Settings for the execution environment.
- Reference note
-
You check the output destination file for thread dumps by monitoring the resource depletion. When there are multiple files in the thread dump output destination (default is work-directory/ejb/J2EE-server-name), multiple system resources (such as the CPU) are consumed in the check processing.