DX Infrastructure Management

An Unknown error (in a browser popup window) occurs randomly at times during the day when users are logged in to UMP (USM).

Restarting wasp alleviates the error temporarily but it reoccurs after a while and it is affecting all users.

An unknown error has occurred.
Refreshing your browser may resolve the issue.

Details:
com.firehunter.ump.exceptions.DataFactoryException : null

Stack Trace:
(80) Session error, Unable to open a client session for 10.1.***.xx:48000: Connection timed out: connect
at com.nimsoft.nimbus.NimNamedClientSession.<init>(NimNamedClientSession.java:37)
at com.nimsoft.nimbus.NimObjectSender.connectNamed(NimObjectSender.java:78)
at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:252)
at com.nimsoft.nimbus.NimRequest.send(NimRequest.java:218)
at com.nimsoft.nimbus.client.core.NimbusProbe.invokeCommand(NimbusProbe.java:68)
at com.nimsoft.nimbus.client.core.NimbusProbe.invokeCommand(NimbusProbe.java:81)
at com.nimsoft.events.api.util.UimUtils.getProbeActiveState(UimUtils.java:130)
at com.nimsoft.events.nas.probe.NasProbe.isRunning(NasProbe.java:32)
at com.nimsoft.events.nas.NasAlarmServiceImpl.getAlarms(NasAlarmServiceImpl.java:64)

Note the trellis references in the body of the stack trace from your unknown error event.

.....
at com.ca.trellis.shift.core.ShiftDispatcher.invoke(ShiftDispatcher.java:137)
at com.ca.trellis.shift.core.ShiftDispatcher.getThrowableObjectEither(ShiftDispatcher.java:84)
at com.ca.trellis.shift.core.ShiftDispatcher.dispatch(ShiftDispatcher.java:44)
at com.ca.trellis.shift.core.TrellisDispatchCoordinator.dispatch(TrellisDispatchCoordinator.java:41)
.....

The nas-api-service package needs updating

1. Download nas-api-service_851.zip (This version is ok to use with UIM 8.47)
    You can download the nas-api-service_851.zip package from the UIM hotfix repository at:

https://www.ca.com/us/services-support/ca-support/ca-support-online/product-content/recommended-reading/technical-document-index/ca-unified-infrastructure-management-hotfix-index.html

 
2. Import this package into your local archive on the primary hub
3. Deploy it to your primary hub
4. Restart the trellis probe
5. The problem should now be resolved and not reoccur.