Error acknowledging alarms in Operator Console
search cancel

Error acknowledging alarms in Operator Console


Article ID: 274231


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)


Suddenly it was not possible to acknowledge alarms from the OC, and error messages appeared in the ems.

The steps in the KB have been followed:

And alarms can now be acknowledged, but the error messages persist in the ems logs 

Aug 30 00:36:02:780 [attach_socket, ems] java.lang.reflect.InvocationTargetException 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke( 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke( 
    at java.lang.reflect.Method.invoke( 
    at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.performCallback( 
    at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.handleMessage( 
    at com.nimsoft.nimbus.NimServerSession$ 
Caused by: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/xxx/xxx_PrimaryHub/xxx/sdgtw_message_hub' 
    at com.nimsoft.nimbus.NimSessionBase.sendRcv( 


Release : 20.3.3/ 20.4 CU8

probe : ems


The root cause of this issue is that whenever we are loading/refreshing the alarm viewer in OC, it triggers an EMS callback which internally calls the sdgtw_message_hub probe which is deprecated now.

So whenever the callback is triggered from OC, it throws the error.

This will be fixed in the upcoming UIM/OC release i.e. 23.4.