6 Replies Latest reply on Aug 9, 2017 1:07 PM by Paulo Dantas

    Need help with setting Tabjolt

    Ajay Gupta

      Hi

      I am having issues in running the stress test using tabjolt. I have followed the documentation in installing and configuring but this error message doesn't go away.

      I have tabjolt installed on a seperate server and Tableau has its own server.

      Failed to connect to the JMX connector due to the following error:
      ConnectException: Connection timed out: connect Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect The Health Service failed to open JMX connection with component:
      vizqlserver, service URL: /jndi/rmi://L4DWEQAP4355:9400/jmxrmi

       

      Please note I have enabled jmx ports by using following commands on tableau server.

      1.tabadmin stop

      2.tabadmin set service.jmx_enabled true

      3.tabadmin configure

      4.tabadmin start

      I enabled the verbose logging and that gave me these error messages.

      <div id="tabBootErr"
      class="tabErrorDialog"><div
      id="tabBootErrTitle">Unexpected Error</div><div
      id="tabBootErrBody">An unexpected error occurred.

      If you continue to receive this error please contact your Tableau
      Server Administrator.<div
      id="tabBootErrMsg"></div></div></div>

      ERROR [2016-11-02 10:28:48,019][InteractVizThreadGroup 1-1] com.tableausoftware.test.server.tabObjects.Viz (Viz.java:1035)   - java.lang.Exception:

      Invalid resp body when calling setSheetId!

       

      ERROR [2016-11-02 10:28:44,238][InteractVizThreadGroup 1-1]
      com.tableausoftware.test.server.perfTestSuite.ViewVizTest
      (InteractVizTest.java:95)   -

      Failed to finish View Viz Test. Site: ClientAnalytics; Workbook:
      UPointOperationsDashboardPreviews; View: CSServiceLevel; IsPublic: false;

      Exception: java.lang.Exception: Invalid resp body when calling
      setSheetId!

      There are no firewall issues ports are opened between two servers. Please note data gets loaded into tables. There were 13 tables created in PerfResults database.

      This is how the whole test ran

      D:\tabjolt>go --t=testplans\InteractVizLoadTest.jmx --d=120 --c=1

      [2016-11-02 21:01:01,889] Perf
      harness is started with parameters: --rootPath=D:\tabjolt
      --t=testplans\InteractVizLoadTest.jmx --d=120 --c=1

      [2016-11-02 21:01:02,107]
      Loading PerfTestConfig yaml file D:\tabjolt\config\PerfTestConfig.yaml

      [2016-11-02 21:01:02,248]
      Loading ServerTestConfig yaml file D:\tabjolt\config\ServerTestConfig.yaml

      -------------start collecting
      JMX counters--------------

      Output
      File:D:\tabjolt/results/2016-11-02_21-01-02/jmxcounter.tsv

      -------------start collecting
      Zabbix counters--------------

      Output
      File:D:\tabjolt/results/2016-11-02_21-01-02/zabbixcounter.tsv

      -------------start windows
      performance counters collection-------------

      Output
      File:d:\tabjolt/results/2016-11-02_21-01-02/wincounter.tsv

      INFO  [2016-11-02
      21:01:04,550][main] (PerfRunHelper.java:346)   - -------------start
      Jmeter load test run-------------

      INFO  [2016-11-02
      21:01:04,550][main] (PerfRunHelper.java:347)   - Output file:
      D:\tabjolt/results/2016-11-02_21-01-02/result-L4DWEQAP4717-0.jtl

      INFO  [2016-11-02
      21:01:04,550][main] (PerfRunHelper.java:348)   - Command:
      [D:\tabjolt/bin/jmeter.bat, , , , , , -n, -t=D:\tabjolt\testplans\InteractVizLoadTest.jmx,

       

      -j=D:\tabjolt/logs/jmeter_2016-11-02_21-01-02.log,
      -JthreadCount=1, -Jduration=120, -JloginWeight=1.0,
      -JconfigFolderPath=D:\tabjolt/config/, -Jlogpath=D:

       

      \tabjolt/results/2016-11-02_21-01-02/result-L4DWEQAP4717-0.jtl,
      ]

      INFO  [2016-11-02
      21:01:04,781][main] (ResultProcessor.java:132)   - -------------start
      processing perf counters and run result-------------

      INFO  [2016-11-02
      21:01:04,781][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-11-02
      21:01:04,812][Thread-13] (PerfRunMonitor.java:37)   - Starting
      Perfrun monitor thread Created the tree successfully using D:\tabjolt\testplans

       

      \InteractVizLoadTest.jmx

      Starting the test @ Wed Nov 02
      21:01:06 CDT 2016 (1478138466031)

      Waiting for possible shutdown
      message on port 4445

      SLF4J: Class path contains
      multiple SLF4J bindings.

      SLF4J: Found binding in
      [jar:file:/D:/tabjolt/lib/slf4j-nop-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]

      SLF4J: Found binding in
      [jar:file:/D:/tabjolt/lib/ext/slf4j-nop-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.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: 9143 Errors: 0

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

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

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: vizqlserver, service URL:
      /jndi/rmi://10.100.80.76:
      9400/jmxrmi

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

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

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

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: vizqlserver, service URL:
      /jndi/rmi://10.100.80.76:9400/jmxrmi

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

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

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

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: vizqlserver, service URL: /jndi/rmi://10.100.80.76:9400/jmxrmi

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

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

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

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: vizqlserver, service URL:
      /jndi/rmi://10.100.80.76:9400/jmxrmi

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

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

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

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

      Tidying up ...  
      @ Wed Nov 02 21:03:11 CDT 2016 (1478138591375)

      ... end of run

      INFO  [2016-11-02
      21:03:24,828][main] (PerfRunHelper.java:195)   - Jmeter process has
      exited. Waiting for the other processes to exit.

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

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

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

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

      INFO  [2016-11-02
      21:03:55,063][main] (PerfRunHelper.java:225)   - Waiting for
      processes "JMX/Zabbix Counter Data Retriever" to complete. 30 seconds
      have elapsed.

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

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

      INFO  [2016-11-02
      21:04:25,375][main] (PerfRunHelper.java:225)   - Waiting for
      processes "JMX/Zabbix Counter Data Retriever" to complete. 60 seconds
      have elapsed.

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

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

      INFO  [2016-11-02
      21:04:55,625][main] (PerfRunHelper.java:225)   - Waiting for
      processes "JMX/Zabbix Counter Data Retriever" to complete. 90 seconds
      have elapsed.

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: dataserver, service URL:
      /jndi/rmi://10.100.80.76:
      10000/jmxrmi

      INFO  [2016-11-02
      21:05:25,938][main] (PerfRunHelper.java:225)   - Waiting for
      processes "JMX/Zabbix Counter Data Retriever" to complete. 120
      seconds have elapsed.

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: dataserver, service URL:
      /jndi/rmi://10.100.80.76:10000/jmxrmi

      INFO  [2016-11-02
      21:05:56,203][main] (PerfRunHelper.java:225)   - Waiting for
      processes "JMX/Zabbix Counter Data Retriever" to complete. 150
      seconds have elapsed.

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: dataserver, service URL:
      /jndi/rmi://10.100.80.76:10000/jmxrmi

      Failed to connect to the JMX
      connector due to the following error: ConnectException: Connection timed out:
      connect

      Failed to get the object from
      the pool due to the following error: ConnectException: Connection timed out:
      connect

      The Health Service failed to
      open JMX connection with component: dataserver, service URL:
      /jndi/rmi://10.100.80.76:10000/jmxrmi

      INFO  [2016-11-02
      21:06:26,469][main] (PerfRunHelper.java:221)   - Timeout of Waiting
      for processes "JMX/Zabbix CounterData Retriever" to complete.
      Killinng the

       

      1. processes.

      INFO  [2016-11-02
      21:06:26,469][main] (PerfRunHelper.java:206)   - killing process
      JMX/Zabbix Counter Data Retriever

      INFO  [2016-11-02
      21:06:26,469][main] (PerfRunHelper.java:208)   - Successfully killed
      process JMX/Zabbix Counter Data Retriever

      INFO  [2016-11-02
      21:06:26,469][main] (PerfRunHelper.java:214)   - All processes have
      exited.

      INFO  [2016-11-02
      21:06:26,469][main] (PerfRunMonitor.java:57)   - Perfrun is completed
      - ending monitor thread

      INFO  [2016-11-02
      21:06:27,641][Thread-7] (JmeterResultDBSender.java:81)   - Finish
      processeing all Jmeter perf result samples.

      INFO  [2016-11-02
      21:06:28,469][Thread-9] (PerfCounterDBSender.java:72)   - Finished
      processing all perf counter records

       

      INFO  [2016-11-02
      21:06:28,485][main] (ResultProcessor.java:190)   -
      -----------------------------------------------------

      INFO  [2016-11-02
      21:06:28,485][main] (ResultProcessor.java:191)   - Perf run result
      have been stored. Please use this RUN ID 11 to view your result in Tableau

        • 1. Re: Need help with setting Tabjolt
          Russell Christopher

          I only see one thing that looks weird here. Your machine name is mentioned:

           

          L4DWEQAP4717

           

          ...yet all of the JMX errors point at an IP address:

           

          10.100.80.76:

           

          Are the error messages you posted from different sessions? Perhaps you fiddled with the config files between sessions?

           

          Also, is the IP address in question correct for L4D* machine?

           

          You've already said you turned on JMX. Good. However, you seem to be saying that you have not opened (On both the Windows OS and on any other appliances you have in place) necessary ports in the firewall. If TabJolt can't get through ports like 9400 and 10000, then the JMX errors would be completely expected.

           

          Please confirm whether you have opened these ports or not.

          • 2. Re: Need help with setting Tabjolt
            Ajay Gupta

            Hi Russ,

            Thanks for responding

            I was testing different things and that may be the reason you are seeing IP address versus name. The IP address is correct. It belongs to that server only.

            Both the servers are in same domain so there are no issue of ports. I have checked the ports using telnet command. Windows firewall is off too.

             

            Regards

            Ajay

            • 3. Re: Need help with setting Tabjolt
              Russell Christopher

              If you're 100% sure there's nothing wrong on the network, then the only thing you really have left is the possibility you made an error with your tabadmin set command. Might want to try it again. I'm not so sure

               

              Also, I'd suggest you take TabJolt out of the picture altogether and attempt to connect to these ports with the Java JMX Console. You might attempt this both on your remote (TabJolt) machine AND the Tableau Server itself to be sure you're not dealing with a Network issue.

               

              You said that you used Telnet to test these ports,  if you can indeed access them, then Tableau is configured correctly because something has to LISTEN on those ports to respond, AND your network should be OK - so BOTH JMX Console and TabJolt should able to connect, too. What you're describing doesn't make a whole lot of sense, which makes me think we're missing a piece of the puzzle here somewhere.

              • 4. Re: Need help with setting Tabjolt
                Ajay Gupta

                Thanks Rob,

                I used JDK (Java Mission Control) to try connecting the tableau server at port 9400-9407 and it didn’t connect , however telnet works fine.

                 

                Regards

                • 5. Re: Need help with setting Tabjolt
                  Russell Christopher

                  Try doing the same thing ON the server and see what happens. I'd also recommend you try re-applying server.jmx_enabled true just be sure it's in there.

                   

                  I've never used telnet against these ports, so I'm not 100% sure that getting "into" the ports themselves means "they work". Typically, we tell people to try the the JMX Console. If that doesn't work, it's a clear sign that there is a firewall issue and/or JMX is NOT enabled.

                   

                  BTW, you are hitting ports for services which exist, right? In other words, are you trying to hit the JMX port for the 2nd VizQLServer process on a machine which doesn't HAVE a 2nd VizQLServer running?

                  • 6. Re: Need help with setting Tabjolt
                    Paulo Dantas

                    Hi Ajay,

                     

                    your question was answered?

                     

                    If yes, choice one answer like correct to close this thread.

                     

                    Cheers.