UMP An Unknown error has occurred

Document ID : KB000033950
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms:

Partial content of the error pop-up window appearing frequently only when USM portlet page is opened:

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

Details:
com.firehunter.ump.exceptions.DataFactoryException : Received status (7) on response (for sendRcv) for cmd = 'nametoip'

Stack Trace:
(7) temporarily out of resources, Received status (7) on response (for sendRcv) for cmd = 'nametoip'
at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:597)
at com.nimsoft.nimbus.NimSessionBase.getHostAndPortForName(NimSessionBase.java:418)
at com.nimsoft.nimbus.NimNamedClientSession.<init>(NimNamedClientSession.java:29)
at com.nimsoft.nimbus.NimObjectSender.connectNamed(NimObjectSender.java:79)
at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:250)
at com.nimsoft.nimbus.pool.NimRequestPool.sendImpersonate(NimRequestPool.java:81)
at com.nimsoft.nimbus.pool.NimRequestPool.send(NimRequestPool.java:66)
at com.nimsoft.nimbus.pool.NimRequestPoolInstance.send(NimRequestPoolInstance.java:180)
at com.nimsoft.nimbus.pool.NimRequestPoolInstance.send(NimRequestPoolInstance.java:150)
at com.firehunter.umpportlet.PDSUtils.send(PDSUtils.java:21)
at com.firehunter.usm.Maintenance.getNextFireTimeFromPDS(Maintenance.java:93)
at com.firehunter.usm.Maintenance.getNextFireTimes(Maintenance.java:76)
at com.firehunter.usm.Maintenance.getSchedules(Maintenance.java:157)
at com.firehunter.usm.Maintenance.getMaintenanceSchedules(Maintenance.java:181)
at com.firehunter.usm.DataFactory.getMaintenanceSchedules(DataFactory.java:7153)
at com.firehunter.usm.DataFactory.getMaintenanceSchedules(DataFactory.java:7145)

 

Environment: 

 

Any UIM/OS Version

 

Cause:

This intermittent error was generated because it appears that the maintenance_mode probe did not start up correctly.

 

Resolution:


The pop-up errors appearing in the UMP USM portlet were stopped by deactivating and activating the maintenance_mode probe.