Skip to main content
NetApp Knowledge Base

Cluster Polling Stuck Due to Concurrency Conflict with EMS Event Processing in AIQUM

Views:
21
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

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]:]

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.