Topic
7 replies Latest Post - ‏2012-12-19T02:37:15Z by zxning
SystemAdmin
SystemAdmin
203 Posts
ACCEPTED ANSWER

Pinned topic Warehouse Administration Console Error - Grid Data Error

‏2012-12-11T15:15:53Z |
Hi all,

has anyone come across an error "Grid Data Error- HTTP Request Error" in Warehouse Administration Console.

We have been using WAS for the last year with no major problems but the last couple of days we have come accross an annoying error.

Under the SQL Warehousing tab, when we click on the Manage Applications sub-tab an error window pops up with Title "Grid Data Error" and a message saying "HTTP Request Error" with all the applications missing. I know the applications are there but they do not show. The other sub-tabs Manage Control Flows, Manage Instances and Manage Schedules work fine. We can deploy a new one but we can not deploy changes because the applications are not shown thus the Deploy changes button is grey :(.
Thanx,

Savvas Savva
Updated on 2012-12-19T02:37:15Z at 2012-12-19T02:37:15Z by zxning
  • glsfromatx
    glsfromatx
    6 Posts
    ACCEPTED ANSWER

    Re: Warehouse Administration Console Error - Grid Data Error

    ‏2012-12-11T15:44:23Z  in response to SystemAdmin
    Whenever I see this error and/or blank screens in the ISW Adminstration Console tabs it is usually due to a problem with the metadata database.

    Common issues:
    1. Metadata Database instance associated with the ISW Administration Console was not started. This can happen after a crash or when bringing a system down for maintenance, since bringing the system up requires one step to start the database instance and a second to start WAS.

    2. ISW Administration Console user password has expired or was changed. ISW connects to its metadata database using an encrypted user/password combination which can lead to failures in the ISW Admin console. See the information link which talks about how passwords changes are handled:

    http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.datatools.accommon.doc/topics/t_wh_pw_ch.html
    Things to check:

    1. Make sure that your metadata database instance is started. If your system has been brought down or restarted it is possible that the db2 instance (if local) was not restarted along with the WebSphere Application Server. This is the most common problem that I've seen when ISW has been working for awhile.

    2. Check the WAS log 'SystemOut.log' in the WebSphere Application Server profiles directory.

    <waspath>/profiles/AppSrv01/logs/server1/SystemOut.log

    where: <waspath> is where WAS is installed, and AppSrv01 is the name of the profile.
    Your system may have a different profile name.
    Look in that WAS log file for jdbc or database connection errors.
  • zxning
    zxning
    20 Posts
    ACCEPTED ANSWER

    Re: Warehouse Administration Console Error - Grid Data Error

    ‏2012-12-12T02:45:28Z  in response to SystemAdmin
    Since the "Manage Control Flows" and "Manage Schedules" tab can be displayed, the metadata db seems to be ok with the connection. We ever met similar problem when there is data inconsistency with the metadata db. Can you check the data records for the table SQWMETA_V3.APPLICATIONS and SQWSTAT_V3.APPSTAT by using following steps:
    1. list all the applications in SQWMETA_V3.APPLICATIONS
    2. check if there is a record in the SQWSTAT_V3.APPSTAT table for each of the applications

    If there are some applications that do not have a related record in the SQWSTAT_V3.APPSTAT table, that might be the root cause for the Grid Data and HTTP Error.
    Pls tell us the result you see from the steps.
    • SystemAdmin
      SystemAdmin
      203 Posts
      ACCEPTED ANSWER

      Re: Warehouse Administration Console Error - Grid Data Error ..

      ‏2012-12-17T12:03:46Z  in response to zxning
      Hello people,

      sorry for the late reply. I have been trying a number of things but I keep hitting dead ends.

      For zxning,

      There is a record in the SQWSTAT_V3.APPSTAT table for each of the applications
      in the SQWMETA_V3.APPLICATIONS.

      There was an error in the db2diag.log of db2 , which unfortunately was not related to be problem. I fixed that. The issue had to do with a tablespace which I increased.

      A few more details about the error.

      The error occured out of the blue. No upgrades, no stop and start WAS or its database. It just happened one day.

      I tried to stop and start WAS and its database. The server and database came up fine and everything is working normally. I even rebooted the machine. We can start control flows, we can see ALL the control flows, we can manage instances with no problems and our scheduler works fine. We can add, delete, change all of them. The problem is that we can not see the applications.

      We get the

      Grid Data Error - HTTP Request Error.

      The funny side of the whole situation is that we can deploy a new application and run its flows but we can not see even the new application in the "Manage Applications" tab.

      Any ideas ?

      Anyone.. In the meantime I have notify the local IBM to open a pmr.

      I have checked all the logs and nothing seems to be recorded as an error. The only thing I get in
      system log is a bunch of entries about

      Annotator registry was not found

      I am posting a couple of messages for reference..
      COM-SRVS SYS-LOG Dec 17, 2012 8:40:01 AM Annotator registry was not found: file:/wasapp/apphome//applications/XXX/etl/analysisengines/.analysisengine.registry.xml

      COM-SRVS SYS-LOG Dec 17, 2012 8:40:01 AM Annotator registry was not found: file:/wasapp/applhome//applications/XXX/etl/analysisengines/.analysisengine.registry.xml

      COM-SRVS SYS-LOG Dec 17, 2012 8:41:00 AM Annotator registry was not found: file:/wasapp/apphome/applications/XXX/etl/analysisengines/.analysisengine.registry.xml
      • SystemAdmin
        SystemAdmin
        203 Posts
        ACCEPTED ANSWER

        Re: Warehouse Administration Console Error - Grid Data Error ..

        ‏2012-12-17T12:17:42Z  in response to SystemAdmin
        If it means anything to anyone I caught this from SystemOut.log
        12/17/12 14:20:09:257 EET 000003bf servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet equinoxbridgeservlet in application IBMDataToolsWeb. Exception created : org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.NullPointerException
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:583)
        at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:104)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
        at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
        at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
        at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
        at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:445)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:504)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:301)
        at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
        Caused by: java.lang.NullPointerException
        at com.ibm.datatools.shared.web.util.grid.AbstractGridDataController.handleGridOperation(AbstractGridDataController.java:227)
        at com.ibm.datatools.shared.web.util.grid.AbstractGridDataController.handleGridOperation(AbstractGridDataController.java:195)
        at com.ibm.datatools.admin.sqw.request.ApplicationDataController.handleRequest(ApplicationDataController.java:132)
        at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
        at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
        at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
        ... 33 more

        12/17/12 14:20:09:271 EET 000003bf webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: Servlet Error-equinoxbridgeservlet: java.lang.NullPointerException
        at com.ibm.datatools.shared.web.util.grid.AbstractGridDataController.handleGridOperation(AbstractGridDataController.java:227)
        at com.ibm.datatools.shared.web.util.grid.AbstractGridDataController.handleGridOperation(AbstractGridDataController.java:195)
        at com.ibm.datatools.admin.sqw.request.ApplicationDataController.handleRequest(ApplicationDataController.java:132)
        at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
        at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
        at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
        at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:104)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
        at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
        at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
        at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
        at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:445)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:504)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:301)
        at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
        • zxning
          zxning
          20 Posts
          ACCEPTED ANSWER

          Re: Warehouse Administration Console Error - Grid Data Error ..

          ‏2012-12-18T02:37:38Z  in response to SystemAdmin
          Hi SavvasCyta :

          Pls see my previous comments and check the points I suggested. If you have any problems in performing the steps, let me know in time.
          • SystemAdmin
            SystemAdmin
            203 Posts
            ACCEPTED ANSWER

            Re: Warehouse Administration Console Error - Grid Data Error ..

            ‏2012-12-18T07:05:46Z  in response to zxning
            Hi zxning,

            I have checked the points you mentioned and there is an entry for every application

            There is a record in the SQWSTAT_V3.APPSTAT table for each of the applications
            in the SQWMETA_V3.APPLICATIONS.

            Have you noticed this error before

            12/17/12 14:20:09:257 EET 000003bf servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet equinoxbridgeservlet in application IBMDataToolsWeb. Exception created : org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.NullPointerException
            • zxning
              zxning
              20 Posts
              ACCEPTED ANSWER

              Re: Warehouse Administration Console Error - Grid Data Error ..

              ‏2012-12-19T02:37:15Z  in response to SystemAdmin
              Hi SavvasCyta:

              1. You can continue to contact IBM for PMR open.
              2. We need to debug on the metadata records, so please export your metadata db and send it to us for a check.