TxPerConnQueueFullDiscard

Measurement Group: Diameter Ingress Transaction Exception

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: The number of egress messages that were discarded because the "Per Connection Egress Message Queue" was full.

Collection Interval: 5 min

Peg Condition: For each message discarded because the "Per Connection Egress Message Queue" was full

Measurement Scope: Server Group

Recovery:

  1. An IP network or Diameter peer problem may exist thus preventing SCTP/TCP from transmitting messages into the network at the same pace that messages are being received from the network.
  2. The transport task associated with the connection may be experiencing a problem preventing it from processing events from its Connection Event Message Queue. Examine the alarm log from Main Menu > Alarms & Events.
  3. If one or more MPs in a server site have failed, the traffic will be distributed amongst the remaining MPs in the server site. Monitor the MP server status from Main Menu > Status & Manage > Server Status.
  4. The mis-configuration of Diameter peers may result in too much traffic being distributed to the MP. Monitor the ingress traffic rate of each MP from Main Menu > Status & Manage > KPIs. Each MP in the server site should be receiving approximately the same ingress transaction per second.
  5. There may be an insufficient number of MPs configured to handle the network traffic load. Monitor the ingress traffic rate of each MP from Main Menu > Status & Manage > KPIs. If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity
  6. If the problem persists, contact My Oracle Support (MOS).
Parent topic: Diameter Ingress Transaction Exception measurements