2 Replies Latest reply on Mar 29, 2016 8:54 AM by jayshaughnessy

    Resource with id (**) does not exist or accessible

    karthikraj
    karthikraj Mar 29, 2016 1:27 AM

      Hello Guys,

       

      I have been using JON 3.3 to monitor EAP applications (testing phase).
      Often i received error in my dashboard like
      "Resource with id [98733] does not exist or is not accessible. This occurred because the server is taking a long time to complete this request. Please be aware that the server may still be processing your request and it may complete shortly. You can check the server logs to see if any abnormal errors occurred."

       

      what the error is trying to say ??? I guess it trying to say one of my servers is  down, if so where could i get those details .
      I checked the logs but I am not able to conclude what it is saying
      Can any one help me what does error insisting??

       

       

      If I am wrong what does the above error means??

       

      10:35:51,693 DEBUG [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/172.34.1.85:7080-4) {CommandProcessor.executing}Executing command [Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=ci.solartis.net, rhq.security-token="", rhq.externalizable-strategy=AGENT, rhq.send-throttle=true, rhq.guaranteed-delivery=true}]; params=[{invocation=NameBasedInvocation[mergeMeasurementReport], targetInterfaceName=org.rhq.core.clientapi.server.measurement.MeasurementServerService}]]

      10:35:51,693 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-4) No java.naming.factory.initial set. Using the default factory.

      10:35:51,693 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-4) No java.naming.factory.initial set. Using the default factory.

      10:35:51,693 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-4) No java.naming.factory.initial set. Using the default factory.

      10:35:51,693 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-4) No java.naming.factory.initial set. Using the default factory.

      10:35:51,693 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (http-/172.34.1.85:7080-4) HibernateStats[ queries=0, xactions=0, loads=0, connects=0, time=0 ] for SLSB:StorageClientManager.getMetricsServer

      10:35:51,693 DEBUG [org.rhq.server.metrics.MetricsServer] (http-/172.34.1.85:7080-4) Inserting 300 raw metrics


      10:37:21,703 DEBUG [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/172.34.1.85:7080-17) {CommandProcessor.executing}Executing command [Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=ci.solartis.net, rhq.security-token=, rhq.externalizable-strategy=AGENT, rhq.send-throttle=true, rhq.guaranteed-delivery=true}]; params=[{invocation=NameBasedInvocation[mergeMeasurementReport], targetInterfaceName=org.rhq.core.clientapi.server.measurement.MeasurementServerService}]]

      10:37:21,703 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-17) No java.naming.factory.initial set. Using the default factory.

      10:37:21,703 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-17) No java.naming.factory.initial set. Using the default factory.

      10:37:21,703 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-17) No java.naming.factory.initial set. Using the default factory.

      10:37:21,703 DEBUG [org.rhq.enterprise.server.naming.AccessCheckingInitialContextFactoryBuilder] (http-/172.34.1.85:7080-17) No java.naming.factory.initial set. Using the default factory.

      10:37:21,703 DEBUG [org.rhq.enterprise.server.util.HibernatePerformanceMonitor] (http-/172.34.1.85:7080-17) HibernateStats[ queries=0, xactions=0, loads=0, connects=0, time=0 ] for SLSB:StorageClientManager.getMetricsServer

      10:37:21,703 DEBUG [org.rhq.server.metrics.MetricsServer] (http-/172.34.1.85:7080-17) Inserting 330 raw metrics


        • 1. Re: Resource with id (**) does not exist or accessible
          pathduck
          pathduck Mar 29, 2016 7:05 AM (in response to karthikraj)

          Hello,

           

          This sometimes happens if you have a lot of resources and try to do changes on them. RHQ/JON tries to avoid causing high cpu so things might instead take some time. Mostly these things can be ignored, but yeah, as a user I'd like to see less of them myself, since when I get them I feel I have to double-check if the operation did what it was supposed to.

           

          Also, if you are using JON you should have support through Redhat, so you would get better attention posting a support case on Red Hat Customer Experience & Engagement - Red Hat Customer Portal

           

          The log you pasted seems to have no relation to the issue by the way, and why are you logging DEBUG? Logging DEBUG might cause more load on the server, and actually cause UI timeout so be careful with that.

            • Actions
          • 2. Re: Resource with id (**) does not exist or accessible
            jayshaughnessy
            jayshaughnessy Mar 29, 2016 8:54 AM (in response to pathduck)

            +1, turn off debug logging unless you are trying to gather information for a support case or bugzilla entry.

             

            That message means that the UI is no longer going to wait for a reply from the server for a requested operation because it's taking the server too long to finish.  It doesn't mean the server is down, or even that the request failed, just that it's taking a while and the UI is no longer going to wait.  If the server failed you'd most likely see ERRORs in the server log.  In general this means that the server is running slowly and/or the request was large, like importing a lot of resources or updating a large number of resources, etc. DB latency is often a reason.  If your DB is on a separate machine from your server, or if your DB is slow for some reason, and the latency is high, it will slow down everything.

              • Actions