Environment
Novell ZENworks Configuration Management 11.2.3a MU1
Situation
After upgrading to ZCM 11.2.3a Monthly Update 1, either or both of the following exceptions are seen in services-messages.log
Case 1 : Getting all device quicktask using API getDeviceAllQuickTasks
[ServiceStoreFactory] [751] [] [java.lang.Exception: DEBUG: Session acquisition stack trace.
at
com.novell.zenworks.datamodel.session.hibernate.SessionMonitor$SessionInfo.<init>(SessionMonitor.java:93)
...
com.novell.zenworks.datamodel.services.quicktasks.QuickTasksAdminImpl.getDeviceAllQuickTasks(QuickTasksAdminImpl.java:656)
Case 2 : Getting ERI info for a device using API getERIInformation
[ServiceStoreFactory] [2414] [] [java.lang.Exception: DEBUG: Session acquisition stack trace.
at
com.novell.zenworks.datamodel.session.hibernate.SessionMonitor$SessionInfo.<init>(SessionMonitor.java:93)
...
at
com.novell.zenworks.datamodel.services.fde.FDEAdminImpl.getERIInformation(FDEAdminImpl.java:383)
Case 1 : Getting all device quicktask using API getDeviceAllQuickTasks
[ServiceStoreFactory] [751] [] [java.lang.Exception: DEBUG: Session acquisition stack trace.
at
com.novell.zenworks.datamodel.session.hibernate.SessionMonitor$SessionInfo.<init>(SessionMonitor.java:93)
...
com.novell.zenworks.datamodel.services.quicktasks.QuickTasksAdminImpl.getDeviceAllQuickTasks(QuickTasksAdminImpl.java:656)
Case 2 : Getting ERI info for a device using API getERIInformation
[ServiceStoreFactory] [2414] [] [java.lang.Exception: DEBUG: Session acquisition stack trace.
at
com.novell.zenworks.datamodel.session.hibernate.SessionMonitor$SessionInfo.<init>(SessionMonitor.java:93)
...
at
com.novell.zenworks.datamodel.services.fde.FDEAdminImpl.getERIInformation(FDEAdminImpl.java:383)
Resolution
This is fixed in version 11.2.4 - see KB 7012027 "ZENworks Configuration Management 11.2.4 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7012027
Cause
A Datamodel session had not been gracefully closed, and the hibernate session cleanup process was forced to close the session. There is no direct impact on functionality