|UMP popup window error
"The backend server has issued an error requiring the client window to close"
The backend server error may only happen when the UMP page sits and no actions are being taken, e,g, mouse movements, refresh page etc.
After the error you may see output in a UMP popup window such as:
Usually caused by signing out from another window.
Details: [ChannelEvent channelId=null reconnecting=true rejected=false type="channelDisconnect" bubbles=false cancelable=false eventPhase=2]
dashboard_engine log may show entries like this:
Mar 09 02:17:05:591 ERROR [MultiInstanceManager, DashboardDesigner:2453] SqlException in getUpdateActions : com.microsoft.sqlserver.jdbc.SQLServerException: Read timed out
com.microsoft.sqlserver.jdbc.SQLServerException: com.microsoft.sqlserver.jdbc.SQLServerException: Read timed out
Mar 09 04:16:23:330 ERROR [OnUpdateDynamicViews-100532, DbProxy:242] Exception in executeGeneralDVQuery while getting results from resultSet: Connection reset
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
wasp log may show errors like:
Mar 25 14:27:29:901 DBLOW [http-8080-12, com.nimsoft.nimbus.probe.service.wasp.udm.CachedAclData] Waiting for the other thread to initialize cache for ACL Superuser
Mar 25 14:27:30:401 DBLOW [http-8080-12, com.nimsoft.nimbus.probe.service.wasp.udm.CachedAclData] Waiting for the other thread to initialize cache for ACL Superuser
A. Scenario 1:
Update interval settings were all set too low, e.g., set to 5 instead of the defaults in the dashboard_engine probe.
Once they were reset to their defaults and dap, dashboard_engine and wasp were restarted, alarms showed up in the UMP alarm console once again and the error no longer occurred..
Default settings for Update Intervals (seconds) is shown below:
If you check the settings in the Raw Configure window versus the GUI you may not notice that the Update Interval settings are set too low so check via the GUI.
B. Scenario 2:
The dashboard_engine out of the box/default settings were no longer sufficient to prevent the backend server error. We modified the dashboard_engine configuration settings to:
Then we clicked Ok to restart the dashboard_engine.
The backend server error no longer occurred.