33008 - DM-IWF maximum pending transactions allowed exceeded

Event Group:

DIWF

Description:

DM-IWF rejected either a Diameter-to-MAP or MAP-to-Diameter transaction because it was unable to allocation a pending transaction record (PTR) for the transaction. DM-IWF allocates a PTR for every pending Diameter-to-MAP and MAP-to-Diameter transaction. If this problem persists and the pool reaches 100% utilization, all new ingress messages will be discarded. This alarm should not normally occur when no other congestion alarms are asserted.

Severity:

Info

Instance:

<DAMPName>

HA Score:

Normal

Throttle Seconds:

10

OID:

eagleXgDiameterDmiwfMaxPendTransactionsAllowedExceededNotify

Recovery:

1. Examine the Alarm log in Alarms & Events a evaluate whether the DSR Application Task might be experiencing a problem processing the messages. The rate of messages being processed by DM-IWF can be monitored from the from Status & Manage > KPIs page
2. If one or more DA-MPs in a server site have failed, this may result in too much traffic being forwarded to the DM-IWF instance reporting this alarm. DA-MP server status can be monitored from the Status & Manage > Server.
3. If one or more DM-IWF instances configured in a server site are unable to provide service, this may result in too much traffic being forwarded to the DM-IWF instance reporting this alarm. DM-IWF application admin state can be monitored from Diameter > Maintenance > Applications. DM-IWF service provider status can be monitored from Communication Agent > Maintenance > Routed Services Status
4. If the problem persists, it is recommended to contact My Oracle Support.