Cluster Polling Stuck Due to Concurrency Conflict with EMS Event Processing in AIQUM
Applies to
- Active IQ Unified Manager (AIQUM) 9.x
- ONTAP Cluster-Mode
Issue
- Cluster polling in Active IQ Unified Manager (AIQUM) intermittently becomes stuck, resulting in missed cluster health updates and lost critical alerts.
- Polling appears stuck in the UI, and subsequent polls are skipped or dropped.
Observed Log Output:
ERROR [oncommand][reconciliation-0][c.n.dfm.collector.OcieJmsListener] Previous foundation poll at <timestamp> ongoing for ds=<id>(<cluster>), adding to the dropped JmsDataSources list...org.springframework.orm.hibernate5.HibernateOptimisticLockingFailureException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update Cluster set healthStatus=? where id=? and healthStatus=?; nested exception is org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update Cluster set healthStatus=? where id=? and healthStatus=?...INFO [oncommand][SyslogServer:udp][c.n.dfm.impl.ems.SysLogEventHandler] Received EMS from: [[<cluster>:cpeer.unavailable:ALERT]:]