Welcome Guest! Log in

Error 404 when trying to open Analytics

    Symptom

    After installing Stambia Analytics 2.2 or higher on an application server running with Java 6, Stambia DI Analytics will not open: the web browser displays an error 404.

    Solution

    Analytics 2.2 and higher require Java 7 or higher. Java 6 is not longer supported starting from Analytics 2.2.

    You can

    • upgrade your server's Java version
    • or install an autonomous JRE 7 for your application server (please consult your application server's documentation to know how)

     

    Statistics view is empty

      Symptom

      When consulting sessions or session details, the Statistics view is empty.

      The Variable view is not empty, only the Statistics view is.

      When going to "Window / Parameters" and the "Statistics" tab, the list is empty.

      Solution

      This is an Analytics Installation issue, concerning new installations made with versions 2.0.9 to 2.1.1.

      Prior versions which were upgraded to 2.0.9 / 2.1.1 are not concerned. New installations made with 2.1.2 or later are not concerned.

      How to fix it:

      • Solution 1:
        • get a "stambia.logs" file from another existing WebappHome directory
        • copy all lines starting with "<logs:statistic" and paste them into the erroneous WebappHome's "stambia.logs" file
      • Solution 2:
        • Go to "Window / Parameters" and the "Statistics" tab
        • Add the following items to the list:
          • Name: WSDL_NB_ERROR, Label: WsdlError
          • Name: SQL_STAT_MERGE, Label: Merge
          • Name: OUT_NB_FILES, Label: OutFileCount
          • Name: SQL_STAT_UPDATE, Label: Update
          • Name: XML_NB_ELEMENTS,  Label: Element
          • Name: SQL_STAT_DELETE, Label: Delete
          • Name: SQL_NB_ROWS, Label: Rows
          • Name: XML_NB_ATTRIBUTES, Label: Attribute
          • Name: SQL_STAT_ERROR, Label: Reject
          • Name: WSDL_NB_DONE, Label: WsdlSuccess
          • Name: SQL_STAT_INSERT, Label: Insert
          • Name: OUT_FILE_SIZE, Label: OutFileSize

      Analytics displays an HTTP Status 500 error

        Symptom

        When trying to access Production Analytics, the following error is displayed in the web browser:

        HTTP Status 500 -

        type Exception report

        message

        description The server encountered an internal error that prevented it from fulfilling this request.

        exception

        java.lang.NullPointerException
            com.indy.ui.analytics.application.Redirect.redirect(Redirect.java:29)
            com.indy.ui.analytics.application.Redirect.doGet(Redirect.java:18)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
            org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
            org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
            org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
            org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
            org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:138)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
            org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

        Solution

        Check that your Analytics URL ends with a trailing slash, for example: http://yourserver:8080/analytics/

        Explanation: This is related to how some versions of Java for Linux process the URLs. Sometimes the trailing slash is automatically added, sometimes not.

        Session timeout when accessing Analytics

          Symptom

          When accessing to Production Analytics, the application raises a "Session timeout" message.

          This may occur immediately or after a delay.

          Solution

          Some Application Servers have no default "session timeout" value, this can produce immediate or too-short session timeouts.

          The session timeout can be configured

          - in the Application Server's settings (see your AS documentation)

          - or in Production Analytics's settings, see this article.

          Knowledge Base

          Suggest a new Article!