2 Replies Latest reply on Oct 28, 2016 4:01 PM by Russell Christopher

    Tabjolt Error-The Health Service failed to open JMX connection with component: vizqlserver#1, service URL: /jndi/rmi://tab216:9401/jmxrmi

    gopi M

      Hi All,

       

           I am new to Tabjolt, i am getting the fallowing error any one please help me in resolving this.

        When i was loading data from Postgres DB1 and DB2 i think i am missing somthing here. and also i am getting the error in JMX counter.

       

        Here i have uploaded the screen shots and config files please check those and let me know where iam missing something.

       

      I am giving my Host name as : tab216 and

      URL : http://192.168.3.216

       

      The Health Service failed to open JMX connection with component: vizqlserver#1, service URL: /jndi/rmi://tab216:9401/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: vizqlserver#1, service URL: /jndi/rmi://tab216:9401/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: vizqlserver#1, service URL: /jndi/rmi://tab216:9401/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: vizqlserver#1, service URL: /jndi/rmi://tab216:9401/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: vizqlserver#1, service URL: /jndi/rmi://tab216:9401/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      Failed to connect to the JMX connector due to the following error: NoSuchObjectException: no such object in table

      Failed to get the object from the pool due to the following error: NoSuchObjectException: no such object in table

      The Health Service failed to open JMX connection with component: dataserver#1, service URL: /jndi/rmi://tab216:10001/jmxrmi

      INFO  [2016-09-28 17:20:59,899][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 30 seconds ha

      ve elapsed.

      INFO  [2016-09-28 17:21:30,319][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 60 seconds ha

      ve elapsed.

      INFO  [2016-09-28 17:22:00,739][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 90 seconds ha

      ve elapsed.

      INFO  [2016-09-28 17:22:31,159][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 120 seconds h

      ave elapsed.

      INFO  [2016-09-28 17:23:01,579][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 150 seconds h

      ave elapsed.

      INFO  [2016-09-28 17:23:31,999][main] (PerfRunHelper.java:158)   - Timeout of Waiting for processes "Windows Perf Counter Data Retriever" to start. Sk

      ip waiting for processes.

      INFO  [2016-09-28 17:23:31,999][main] (PerfRunHelper.java:346)   - -------------start Jmeter load test run-------------

      INFO  [2016-09-28 17:23:31,999][main] (PerfRunHelper.java:347)   - Output file: C:\Users\Administrator\Desktop\TabjoltForTableauServer9.0To9.3/results

      /2016-09-28_17-20-29/result-tab216-0.jtl

      INFO  [2016-09-28 17:23:31,999][main] (PerfRunHelper.java:348)   - Command: [C:\Users\Administrator\Desktop\TabjoltForTableauServer9.0To9.3/bin/jmeter

      .bat, , , , , , -n, -t=C:\Users\Administrator\Desktop\TabjoltForTableauServer9.0To9.3\testplans\InteractVizLoadTest.jmx, -j=C:\Users\Administrator\Des

      ktop\TabjoltForTableauServer9.0To9.3/logs/jmeter_2016-09-28_17-20-29.log, -JthreadCount=1, -Jduration=20, -JloginWeight=1.0, -JconfigFolderPath=C:\Use

      rs\Administrator\Desktop\TabjoltForTableauServer9.0To9.3/config/, -Jlogpath=C:\Users\Administrator\Desktop\TabjoltForTableauServer9.0To9.3/results/201

      6-09-28_17-20-29/result-tab216-0.jtl, ]

      INFO  [2016-09-28 17:23:32,142][main] (ResultProcessor.java:132)   - -------------start processing perf counters and run result-------------

      INFO  [2016-09-28 17:23:32,142][main] (ResultProcessor.java:133)   - Perf run result is saving to result repository. Please use this RUN ID 11 to view

      your result in Tableau

      INFO  [2016-09-28 17:23:32,158][Thread-12] (PerfRunMonitor.java:37)   - Starting Perfrun monitor thread

      Created the tree successfully using C:\Users\Administrator\Desktop\TabjoltForTableauServer9.0To9.3\testplans\InteractVizLoadTest.jmx

      Starting the test @ Wed Sep 28 17:23:32 EDT 2016 (1475097812829)

      Waiting for possible shutdown message on port 4445

      SLF4J: Class path contains multiple SLF4J bindings.

      SLF4J: Found binding in [jar:file:/C:/Users/Administrator/Desktop/TabjoltForTableauServer9.0To9.3/lib/slf4j-nop-1.7.5.jar!/org/slf4j/impl/StaticLogger

      Binder.class]

      SLF4J: Found binding in [jar:file:/C:/Users/Administrator/Desktop/TabjoltForTableauServer9.0To9.3/lib/ext/slf4j-nop-1.7.7.jar!/org/slf4j/impl/StaticLo

      ggerBinder.class]

      SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

      SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

      #0      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 2879 Errors: 0

      #1      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 1041 Errors: 0

      #2      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 804  Errors: 0

      #3      Threads: 1/1    Samples: 2      Latency: 0      Resp.Time: 880  Errors: 0

      #4      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 713  Errors: 0

      #5      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 843  Errors: 0

      #6      Threads: 1/1    Samples: 2      Latency: 0      Resp.Time: 746  Errors: 0

      #7      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 654  Errors: 0

      #8      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 653  Errors: 0

      #9      Threads: 1/1    Samples: 2      Latency: 0      Resp.Time: 701  Errors: 0

      #10     Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 642  Errors: 0

      #11     Threads: 1/1    Samples: 2      Latency: 0      Resp.Time: 682  Errors: 0

      #12     Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 653  Errors: 0

      #13     Threads: 1/1    Samples: 2      Latency: 0      Resp.Time: 662  Errors: 0

      #14     Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 653  Errors: 0

      #15     Threads: 1/1    Samples: 2      Latency: 0      Resp.Time: 787  Errors: 0

      #16     Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 688  Errors: 0

      Tidying up ...    @ Wed Sep 28 17:23:54 EDT 2016 (1475097834950)

      ... end of run

      INFO  [2016-09-28 17:24:12,188][main] (PerfRunHelper.java:195)   - Jmeter process has exited. Waiting for the other processes to exit.

      INFO  [2016-09-28 17:24:12,188][main] (PerfRunHelper.java:214)   - All processes have exited.

      INFO  [2016-09-28 17:24:12,188][main] (PerfRunMonitor.java:57)   - Perfrun is completed - ending monitor thread

      INFO  [2016-09-28 17:24:12,843][Thread-9] (PerfCounterDBSender.java:72)   - Finished processing all perf counter records

      INFO  [2016-09-28 17:24:14,075][Thread-7] (JmeterResultDBSender.java:81)   - Finish processeing all Jmeter perf result samples.

      INFO  [2016-09-28 17:24:14,106][main] (ResultProcessor.java:190)   - -----------------------------------------------------

      INFO  [2016-09-28 17:24:14,106][main] (ResultProcessor.java:191)   - Perf run result have been stored. Please use this RUN ID 11 to view your result i

      n Tableau

       

       

      C:\Users\Administrator\Desktop\TabjoltForTableauServer9.0To9.3>