Tech Tip: UIM - After upgrading from 8.5 to 8.5.1, custom dashboard is not working

Document created by danst04 Employee on Mar 21, 2017
Version 1Show Document
  • View in full screen mode


After upgrading to 8.5.1 I cannot create QOS graphs in the custom dashboard when picking a QOS data source.  When I try to test the results using the dashboard portlet, I get this error:
Recipient[Actor[AKKA://dashboard/user/dao-router]]had already been terminated.



- UIM 8.5 upgraded to 8.5.1


dashboard portlet was in a bad state following upgrade to 8.5.1.

Stack Trace:

Deprecation warning: moment().subtract(period, number) is deprecated. Please use moment().subtract(number, period).
X @ main.js:835
http://<hostname>/dashboard/api/data Failed to load resource: the server responded with a status of 500 (Internal Server
main.js:781 [ERROR] [9:30:4] {"status":500,"message":"cannot create children while terminating or terminated","stackTrace":
["java.lang.IllegalStateException: cannot create children while terminating or terminated","at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)","at sun.reflect.NativeMethodAccessorImpl.invoke

main.js:781 [ERROR] [9:30:4] Error getting request to start data polling
error @ main.js:781
http://wbazpruimump01/dashboard/api/data/source/qos/test Failed to load resource: the server responded with a status of 408
(Request Timeout)
main.js:781 [ERROR] [9:31:9] {"status":408,"message":"Recipient[Actor[akka://dashboard/user/dao-router]] had already been
terminated.","stackTrace":["akka.pattern.AskTimeoutException: Recipient[Actor[akka://dashboard/user/dao-router]] had already
been terminated.","at akka.pattern.AskSupport$class.ask(AskSupport.scala:79)","at akka.pattern.package$.ask
(package.scala:41)","at akka.pattern.Patterns$.ask(Patterns.scala:78)","at akka.pattern.Patterns.ask(Patterns.scala)","at



To work around the problem, we did the following:

1. Open the wasp probe GUI using IM
2. Choose webapps Tab
3. Restart the dashboard portlet webapp

Data was then displayed in the dashboard when we returned to viewing it.

Test of the QOS also displayed QOS results as expected.

3 people found this helpful