If a MID Server has one or more extension listeners, and the MID loses connectivity to the instance and the MID is part of a cluster, the failover business rule will restart the listener on another MID in that cluster.  If, at a later time, the MID that originally lost connectivity comes back online, it will still be running the extension listener, resulting in duplicate events being sent to the instance. 

Sometimes when failover occurs in a MID cluster for SNMP traps, you might see duplicate events in em_event. When checking the MID server threads, you see that "Trap" threads are running on both MID servers instead of just the active one defined in the SNMP Trap Extension. Other extensions could also be affected in similar ways including vCenter, Event Management, and MID Web Server.

Steps to Reproduce

  1. Cause failover of "Failover" MID Server cluster for SNMP Trap Extension (ideally by MID connectivity interruption to instance i.e., temporarily restrict firewall rules).
  2. Verify the failover. Extension started on other cluster member MID Server.
  3. Resume connectivity of previously primary MID Server.
  4. Validate that trap threads are running on both MID Servers.
  5. Send SNMP traps to both MID Servers and note parallel processing. Duplicate events are seen in em_event.


Restart the MID that is still listening.

Related Problem: PRB1326217

Seen In

There is no data to report.

Fixed In

New York

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:43:34