跳转到主内容

修复 AIQUM 中的维护窗口初始化错误

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

适用于

  • Active IQ Unified Manager 9.18+ (AIQUM)

问题

  • 每次尝试 WildFly 重新启动时,AIQUM Web 应用程序(dfm-app.war)都无法启动。
  • 以下异常出现在 WildFly 服务器日志中:
    org.hibernate.LazyInitializationException: could not initialize proxy [MaintenanceWindow#1] - no Session
  • 当数据库中存在 ID=1 的维护窗口记录时,将触发此问题。

原因

  • MaintenanceWindowScheduler.init() 方法在 dfm-app.war 中访问了一个 Hibernate 延迟代理(MaintenanceWindow#1),但此时没有处于活动状态的会话。
  • 这是在 9.18P1 版本的代码/映射更改中引入的。

解决方案

合作伙伴备注

 

追加信息

 

内部参考

  • 这是一个 L2 操作,需要在 AIQUM 设备上直接访问数据库。

已 为此问题提交 CAIQUM-8929

  • L2 过程—数据库清理:
  1. 连接到 AIQUM 设备上的 MySQL,然后选择Ocum数据库。
  2. 选择 Ocum 数据库
    USE OCUM;
  3. 检查当前维护窗口状态:
    SELECT mw.id, FROM_UNIXTIME(mw.startTime/1000) AS start_time, FROM_UNIXTIME(mw.endTime/1000) AS end_time, m.resourceType, m.resourceId
    FROM maintenance_window mw
    LEFT JOIN maintenance_window_object_mapping m ON m.maintenanceWindowId = mw.id;
  4. 删除所有维护窗口记录(ON DELETE CASCADE自动清理maintenance_window_object_mapping):
    DELETE FROM maintenance_window;
  5. 验证两个表均为空:
    SELECT COUNT(*) FROM maintenance_window;
    SELECT COUNT(*) FROM maintenance_window_object_mapping;
  6. 重新启动 AIQUM 服务器。

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.