The following table describes the information output in monitoring information of memory depletion:

Table 4-6 Contents output in monitoring information for memory depletion

Note

The prerequisite of the function for monitoring memory depletion is a system tuned in such a way that the full garbage collection does not occur since sufficient memory is designed. The purpose of this function for monitoring memory depletion is to detect in advance the temporary termination of an application due to full garbage collection, even in a system tuned in such a way. Note that if the memory tuning is insufficient, unnecessary alerts may be output.

When monitoring memory depletion, we recommend that you specify the same value for the maximum size and initial size of the Permanent area. To be more precise, set the same value for the -XX:MaxPermSize and -XX:PermSize of usrconf.cfg. If different values are specified, alerts might be issued even during the expansion of the Permanent area. For details on other tuning parameters, see the information on the Oracle website.

A full garbage collection does not necessarily occur when the memory usage being monitored by this functionality reaches 100%. The monitored value is used for predicting if there is a high possibility of the occurrence of full garbage collection.

The Java heap is now used effectively such that the full garbage collection does not easily occur from Application Server 09-00 onwards. Due to this, the system continues to operate while the usage rate of the Java heap is high, and an unnecessary alert might be output. In such cases, adjust the threshold value.

Reference note

The heap and memory of JavaVM contain the following three types of areas:

• New area
  This area is applicable to Eden and Survivor. This area stores new objects.
  
• Old area
  This area is applicable to Tenured. This area stores objects existing for a long time.
  
• Permanent area
  This area stores classes loaded in JavaVM.
  

The Information of free area, occupied area, and maximum area size for each of these areas at that point of time is output in memory monitoring result.

If memory monitoring is set, messages are output in the following cases:

• If the occupied size of the Old area corresponding to the total size of the Old area exceeds the threshold value
  The message is output if "Occupied size of Old area / Total size of Old area x 100threshold value(%)".
  
• If the total size of the New area corresponding to the maximum free size of the Old area exceeds the threshold value
  The message is output if "Total size of New area / Maximum free size of Old area x 100threshold value(%)".
  
• If the occupied size of the Permanent area corresponding to the total size of the Permanent area exceeds the threshold value
  The message is output if "Occupied size of Permanent area / Total size of Permanent area x 100threshold value(%)".
  

The following table describes the information output in the result of monitoring file descriptors information. You cannot monitor the number of file descriptors in Windows or AIX.

Table 4-7 Contents output in the monitoring information for depletion of file descriptors

The following table describes the information output in monitoring information of thread depletion:

Table 4-8 Contents output in the monitoring information for thread depletion

The following table describes the information output in the monitoring information of depletion of thread dump:

Table 4-9 Contents output in the monitoring information for thread dump depletion

The queue of HTTP requests pending execution is the pending queue for Web applications and the default pending queue corresponding to the concurrently executing threads of the Web application.

The following table describes the information output in the monitoring information depletion of queue of HTTP request pending execution. This depletion monitoring information includes the following two types of information:

• Result of monitoring the number of default stored requests of the pending queues for each J2EE server.
• Result of monitoring the number of stored queues of requests pending execution for each Web application.
  

  Table 4-10 Contents output in the monitoring information for depletion of HTTP requests pending queue

  Character string of output title	Output contents
  J2eeApplicationName	The J2EE application name is output. For monitoring results of default queue of requests pending execution, "-" is output.
  ContextRootName	Context root name is output. For monitoring results of default queue of requests pending execution, "-" is output.
  Rate	The percentage of the number of currently stored queues corresponding to its maximum value is output. The unit is %.
  Current	The current value of the number of stored queues is output.
  Max	The maximum value of the number of requests stored in the pending queue for Web applications and the default pending queue is output.
  Threshold	Threshold value is output. The unit is %.

The following table describes the information output in monitoring information of the number of depleted sessions:

Table 4-11 Contents output in the monitoring information for depletion of the number of sessions

The following table describes the information output in monitoring information of depletion of a connection pool:

Table 4-12 Contents output in the monitoring information for connection pool depletion

#

Depending on the timing when the connection is established, a value greater than All might be output to Current temporarily.