19806 - Communication Agent CommMessage Mempool Utilization

Alarm Group:

CAF

Description:

The percent utilization of the Communication Agent internal resource pool (CommMessage) is approaching its defined capacity. If this problem persists and the usage reaches 100% utilization, ComAgent allocates the CommMessage objects from the heap. This should not impact the functionality, but may impact performance and/or latency.

Severity:

Critical, Major, Minor

Instance:

<ComAgent Process Name>

HA Score:

Normal

Auto Clear Seconds:

0 (zero)

OID:

cAFPoolResUtilNotify

Cause:

This alarm raises when ComAgent mempool utilization exceeds threshold limits. Minor (>= 60%), Major (>=80% ), Critical (>=95%), % level of Max = 65535.

Diagnostic Information:

The percent utilization of the Communication Agent internal resource pool, CommMessage is approaching its defined capacity. If this problem persists and the usage reaches 100% utilization, ComAgent will allocate the CommMessage objects from the heap. This should not impact the functionality, but may impact performance and/or latency.

This alarm usually occurs when other congestion alarms are asserted. This may occur for one of the following reasons:

• An IP network or adjacent node problem may exist preventing from transmitting messages into the network at the same pace that messages are being received from the network.
• The Task thread may be experiencing a problem preventing it from processing events from its internal resource queue.
• The mis-configuration of adjacent node IP routing may result in too much traffic being distributed to the MP.
• There may be an insufficient number of MPs configured to handle the network traffic load.

Recovery:

1. Navigate to Alarms & Events to examine the alarm log.

   An IP network or Adjacent node problem may exist preventing from transmitting messages into the network at the same pace that messages are being received from the network. The Task thread may be experiencing a problem preventing it from processing events from its internal resource queue. It is recommended to contact My Oracle Support for assistance.

2. Navigate to Status & Manage > KPIs to monitor the ingress traffic rate of each MP.

   Each MP in the server site should be receiving approximately the same ingress transaction per second.

   It is recommended to contact My Oracle Support for assistance.

3. If the MP ingress rate is approximately the same, there may be an insufficient number of MPs configured to handle the network traffic load.

   If all MPs are in a congestion state then the ingres rate to the server site is exceeding its capacity.

   It is recommended to contact My Oracle Support for assistance.