UMP is showing error about dispatch

Document ID : KB000107995
Last Modified Date : 26/07/2018
Show Technical Document Details
Issue:
When opening UMP or USM you get the bellow error:

 "An unknown error has occurred. Refreshing your browser may resolve the issue. Details: com.firehunter.ump.exceptions.DataFactoryException : java.lang.RuntimeException: (120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'dispatcher' Please check the log for more information. Stack Trace: (1) error, java.lang.RuntimeException: (120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'dispatcher': (120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'dispatcher' at com.nimsoft.events.client.EmsClient.handleServiceException(EmsClient.java:778) at com.nimsoft.events.client.EmsClient.getAlarmsFromService(EmsClient.java:79) at com.nimsoft.events.client.EmsClient.getAlarms(EmsClient.java:58) at com.firehunter.usm.alarms.EmsAlarmProvider.getAlarmsResult(EmsAlarmProvider.java:93) at com.firehunter.usm.alarms.EmsAlarmProvider.getAlarmUpdates(EmsAlarmProvider.java:60) at com.firehunter.usm.AlarmUtils.getAlarmsFromDb(AlarmUtils.java:320) at com.firehunter.usm.AlarmUtils.getAlarms(AlarmUtils.java:82) at com.firehunter.usm.DataFactory.getAlarms(DataFactory.java:1078) at com.firehunter.usm.DataFactory.getAlarms(DataFactory.java:1070) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:421) at flex.messaging.services.RemotingService.serviceMessage(RemotingService.java:183) at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1503) at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:884) at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:121) at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158) at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:44) at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:67) at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:146) at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:278) at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:322) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at com.firehunter.ump.auth.InvalidHttpSessionFilter.doFilter(InvalidHttpSessionFilter.java:29) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) "
Cause:
This might be caused by NAS probe being stalled.
Resolution:
Restart or redeploy NAS probe usually fixes the issue.
 
Additional Information:
If the issue persists please open a support case with CA.