19807 - Communication Agent User Data FIFO Queue Utilization

Alarm Group:

CAF

Description:

The percent utilization of the Communication Agent User Data FIFO queue is approaching defined threshold capacity. If this problem persists and the queue reaches above the defined threshold utilization, the new StackEvents (Query/Response/Relay) messages for the Task can be discarded, based on the StackEvent priority and Application's Global Congestion Threshold Enforcement Mode.

Severity:

Minor, Major, Critical

Instance:

<ComAgent StackTask Name>

HA Score:

Normal

Auto Clear Seconds:

0 (zero)

OID:

cAFUserDataFIFOUtilNotify

Cause:

Minor (>= 60%), Major (>=80% ), Critical (>=95%), Percentage level of Max = 8000

Diagnostic Information:

The percent utilization of the Communication Agent User Data FIFO queue is approaching its defined capacity. If this problem persists and the queue reaches above the defined threshold utilization, the new StackEvents (Query/Response/Relay) messages for the Task can be discarded, based on the StackEvent priority and Application's Global Congestion Threshold Enforcement Mode. This alarm should not normally occur when no other congestion alarms are asserted.

Recovery:

1. Navigate to Alarms & Events to examine the alarm log and determine if the ComAgent worker thread may be experiencing a problem preventing it from processing events from User Data FIFO queue.
2. Navigate to Status & Manage > KPIs to monitor the ingress traffic rate of each MP.
   • Mis-configuration of routing may result in unbalanced traffic directed to the MP. Under balanced traffic distribution, each MP should be receiving approximately the same ingress transaction per second.
   • 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 offered load to the server site is exceeding its capacity.
3. There may be an issue with network that causes lot of ComAgent connection setup and handshake messages. Check network latency and stability parameters.
4. If the problem persists, it is recommended to contact My Oracle Support for assistance.