DX Unified Infrastructure Management

 View Only
Expand all | Collapse all

Dashboard Designer UMP 20.1

  • 1.  Dashboard Designer UMP 20.1

    Posted Jun 04, 2020 09:30 PM
    Hi y'all, 

    On a customer, UIM 9.20 was implemented, running smoothly, configured to enter the UMP via HTTPS.

    Recently, the migration to version 20.1 was done. And we found, specifically in the Dashboard Designer that it was not possible to create, modify or delete Dashboards, indicating an error, as seen in the following example image. 

    In addition, the dashboards created before the migration now do not receive the data. It should be clarified that this happens when accessing the dashboard portlet via HTTPS. 
    Now, when you enter by port 80, via HTTP: http://<domain name>/dashboard, it's possible to create, modify or delete dashboard. The dashboards created before will show the data, but when you want to open another dashboard from the list, it will be empty.



    Someone knows what this failure is due to, if it's a communication failure or an error in the new version.

    UIM/UMP 20.1

    ------------------------------
    IT Consultant
    IT Business Solutions
    ------------------------------


  • 2.  RE: Dashboard Designer UMP 20.1

    Broadcom Employee
    Posted Jun 04, 2020 09:43 PM
    Hi 

    Please check after clearing browser cache from beginning of time and on different browsers which is required after any upgrade


  • 3.  RE: Dashboard Designer UMP 20.1

    Posted Jun 05, 2020 09:42 AM
    The browsers were cleaned after the migration.

    Following your suggestion, I tried different browsers: the error occurs in Chrome, Edge and Explorer, while in FireFox and Brave it works correctly.

    ------------------------------
    IT Consultant
    IT Business Solutions
    ------------------------------



  • 4.  RE: Dashboard Designer UMP 20.1

    Broadcom Employee
    Posted Jun 04, 2020 09:52 PM
    Hi Reinaldo,

    Any errors in the wasp.log at loglevel 5,or portal.log or error output from the Browser Developer Tools (F12) when accessing the designer?

    Steve

    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 5.  RE: Dashboard Designer UMP 20.1

    Posted Jun 05, 2020 09:48 AM
    Hi Steve, 

    No errors are indicated in the logs, but when you check the Browser Developer Tools, they are presented when you try to make a change in the dashboard designer.
    These failures occur with Chrome, Edge and Explorer. In other browsers like FireFox and Brave it works fine.

    These are the errors: 
    main.js:766 PUT https://sadcwmo09/dashboard/api/definition/dee3c87d-47a2-4b14-baa6-d8b18fb19505 400
    send @ main.js:766
    ajax @ main.js:766
    request @ main.js:769
    saveDashboard @ main.js:875
    F @ main.js:883
    u @ main.js:769
    trigger @ main.js:769
    (anonymous) @ main.js:873
    (anonymous) @ main.js:873
    dispatch @ main.js:765
    m.handle @ main.js:765
    main.js:769 [ERROR] [9:1:23] {"status":400,"message":"Required request body content is missing: org.springframework.web.method.HandlerMethod$HandlerMethodParameter@44d8b8cb","stackTrace":["org.springframework.http.converter.HttpMessageNotReadableException: Required request body content is missing: org.springframework.web.method.HandlerMethod$HandlerMethodParameter@44d8b8cb","at org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.handleEmptyBody(RequestResponseBodyMethodProcessor.java:189)","at org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.readWithMessageConverters(RequestResponseBodyMethodProcessor.java:170)","at org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.resolveArgument(RequestResponseBodyMethodProcessor.java:105)","at org.springframework.web.method.support.HandlerMethodArgumentResolverComposite.resolveArgument(HandlerMethodArgumentResolverComposite.java:77)","at org.springframework.web.method.support.InvocableHandlerMethod.getMethodArgumentValues(InvocableHandlerMethod.java:162)","at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:129)","at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)","at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:777)","at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:706)","at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)","at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:943)","at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:877)","at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:966)","at org.springframework.web.servlet.FrameworkServlet.doPut(FrameworkServlet.java:879)","at javax.servlet.http.HttpServlet.service(HttpServlet.java:663)","at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:842)","at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)","at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)","at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)","at com.firehunter.dashboard.config.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:33)","at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)","at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:73)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:117)","at sun.reflect.GeneratedMethodAccessor600.invoke(Unknown Source)","at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)","at java.lang.reflect.Method.invoke(Method.java:498)","at com.liferay.portal.kernel.bean.ClassLoaderBeanHandler.invoke(ClassLoaderBeanHandler.java:67)","at com.sun.proxy.$Proxy1249.doFilter(Unknown Source)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:73)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.processDirectCallFilter(InvokerFilterChain.java:168)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:96)","at com.liferay.portal.kernel.servlet.PortalClassLoaderFilter.doFilter(PortalClassLoaderFilter.java:74)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.processDoFilter(InvokerFilterChain.java:207)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:109)","at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:108)","at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)","at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)","at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)","at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)","at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:666)","at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)","at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)","at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)","at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)","at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367)","at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)","at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)","at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639)","at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)","at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)","at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)","at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)","at java.lang.Thread.run(Thread.java:748)"]}
    error @ main.js:769
    error @ main.js:769
    h @ main.js:765
    fireWith @ main.js:765
    i @ main.js:766
    t @ main.js:766
    XMLHttpRequest.send (async)
    send @ main.js:766
    ajax @ main.js:766
    request @ main.js:769
    saveDashboard @ main.js:875
    F @ main.js:883
    u @ main.js:769
    trigger @ main.js:769
    (anonymous) @ main.js:873
    (anonymous) @ main.js:873
    dispatch @ main.js:765
    m.handle @ main.js:765
    main.js:769 [ERROR] [9:1:23] Error saving your dashboard
    error @ main.js:769
    r @ main.js:770
    u @ main.js:769
    trigger @ main.js:769
    (anonymous) @ main.js:883
    h @ main.js:765
    fireWith @ main.js:765
    (anonymous) @ main.js:765
    h @ main.js:765
    fireWith @ main.js:765
    i @ main.js:766
    t @ main.js:766
    XMLHttpRequest.send (async)
    send @ main.js:766
    ajax @ main.js:766
    request @ main.js:769
    saveDashboard @ main.js:875
    F @ main.js:883
    u @ main.js:769
    trigger @ main.js:769
    (anonymous) @ main.js:873
    (anonymous) @ main.js:873
    dispatch @ main.js:765
    m.handle @ main.js:765


    Is it possible that this is due to the implemented security certificate?

    ------------------------------
    IT Consultant
    IT Business Solutions
    ------------------------------



  • 6.  RE: Dashboard Designer UMP 20.1

    Posted Jun 05, 2020 09:56 AM
    Based on some prior instances of this problem with earlier versions of uim try this:
    deactivate wasp
    rename the \wasp\work folder 
    rename the \wasp\webapps\dashboard folder 
    rename the \wasp\webapps\dashboard.war file 
    deploy the ump_dashboard 20.1 version from the archive to the ump machine.
    Actiavte wasp

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 7.  RE: Dashboard Designer UMP 20.1

    Posted Jun 05, 2020 08:18 PM
    David, 

    Could you give me an example of which or how I could rename the files and folders you indicate, and how this does not impact on the probe's restart.
    What name should I put when I rename? or I just click on rename without actually changing the name.



    ------------------------------
    IT Consultant
    IT Business Solutions
    ------------------------------



  • 8.  RE: Dashboard Designer UMP 20.1

    Posted Jun 08, 2020 07:25 AM
    the name doesn't matter 
    rename the \wasp\work folder  < automatically rebuilt upon wasp activation
    rename the \wasp\webapps\dashboard folder  < replaced with the deployment of  ump_dashboard
    rename the \wasp\webapps\dashboard.war file < replaced with the deployment of  ump_dashboard

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 9.  RE: Dashboard Designer UMP 20.1

    Broadcom Employee
    Posted Jun 05, 2020 09:57 AM
    Are you using a self-signed SSL cert or a valid Signed SSL cert?
    Do you get errors when accessing the HTTPS?
    If you are using a SIGNED SSL cert I would not expect this to cause a problem.
    If you are using the UMP generated Self Signed SSL cert I would not expect a problem
    You might want to disable the wasp probe and try doing the following
    1) rename the wasp\work folder
    2) rename the wasp\webapps\root
    3) go to c:\windows\temp or /tmp and delete the contents
    activate wasp and test.

    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------



  • 10.  RE: Dashboard Designer UMP 20.1

    Posted Jun 05, 2020 12:14 PM
    The certificate is self-signed, provided by the client.
    Each new connection in a browser, this the message that appears before entering:



    Could the above procedure resolve this incident?

    Reinaldo


    ------------------------------
    IT Consultant
    IT Business Solutions
    ------------------------------



  • 11.  RE: Dashboard Designer UMP 20.1

    Broadcom Employee
    Posted Jun 05, 2020 12:15 PM
    I would try switching back to the UMP generated SELF signed SSL cert and see if that corrects it or install a VALID SSL cert as this works fine over HTTP

    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------



  • 12.  RE: Dashboard Designer UMP 20.1
    Best Answer

    Broadcom Employee
    Posted Jun 05, 2020 10:17 AM
    Hi Reinaldo,

    This may be due to a very recent issue we discovered in the version of Apache Tomcat (embedded) we are using which affects Admin Console and possibly UMP when using HTTPS. If I provide you with the updated jar files, can you test this in a Test/Dev environment?

    Steve

    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------