5 Replies Latest reply on Jul 23, 2016 11:41 PM by Russell Christopher

    Tabjolt - division by zero

    Zach Krzyzanowski
    Zach Krzyzanowski Jul 15, 2016 12:53 PM

      Hi,

      I'm trying to run TabJolt on a virtual machine on my laptop to a Tableau server that isn't attached to any domain.  I'm receiving the following output:

       

       

      C:\tabjolt>go --t=testplans\ViewVizLoadTest.jmx --d=10 --c=1
      [2016-07-15 15:29:44,110] Perf harness is started with parameters: --rootPath=C:\tabjolt --t=testplans\ViewVizLoadTest.jmx --d=10 --c=1
      [2016-07-15 15:29:44,360] Loading PerfTestConfig yaml file C:\tabjolt\config\PerfTestConfig.yaml
      [2016-07-15 15:29:44,594] Loading ServerTestConfig yaml file C:\tabjolt\config\ServerTestConfig.yaml
      -------------start collecting JMX counters--------------
      Output File:C:\tabjolt/results/2016-07-15_15-29-44/jmxcounter.tsv
      -------------start collecting Zabbix counters--------------
      Output File:C:\tabjolt/results/2016-07-15_15-29-44/zabbixcounter.tsv
      -------------start windows performance counters collection-------------
      Output File:c:\tabjolt/results/2016-07-15_15-29-44/wincounter.tsv
      INFO  [2016-07-15 15:30:05,157][main] (PerfRunHelper.java:346)   - -------------start Jmeter load test run-------------
      INFO  [2016-07-15 15:30:05,157][main] (PerfRunHelper.java:347)   - Output file: C:\tabjolt/results/2016-07-15_15-29-44/result-DESKTOP-RD85OP1-0.jtl
      INFO  [2016-07-15 15:30:05,157][main] (PerfRunHelper.java:348)   - Command: [C:\tabjolt/bin/jmeter.bat, , , , , , -n, -t=C:\tabjolt\testplans\ViewVizLoadTest.jmx, -j=C:\tabjolt/logs/jmeter_2016-07-15_15-29-44.log, -JthreadCount=1, -Jduration=10, -JloginWeight=1.0, -JconfigFolderPath=C:\tabjolt/config/, -Jlogpath=C:\tabjolt/results/2016-07-15_15-29-44/result-DESKTOP-RD85OP1-0.jtl, ]
      INFO  [2016-07-15 15:30:05,379][main] (ResultProcessor.java:132)   - -------------start processing perf counters and run result-------------
      INFO  [2016-07-15 15:30:05,384][main] (ResultProcessor.java:133)   - Perf run result is saving to result repository. Please use this RUN ID 30 to view your result in Tableau
      INFO  [2016-07-15 15:30:05,422][Thread-13] (PerfRunMonitor.java:37)   - Starting Perfrun monitor thread
      Created the tree successfully using C:\tabjolt\testplans\ViewVizLoadTest.jmx
      Starting the test @ Fri Jul 15 15:30:06 PDT 2016 (1468621806866)
      Waiting for possible shutdown message on port 4445
      SLF4J: Class path contains multiple SLF4J bindings.
      SLF4J: Found binding in [jar:file:/C:/tabjolt/lib/slf4j-nop-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
      SLF4J: Found binding in [jar:file:/C:/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]
      Tidying up ...    @ Fri Jul 15 15:30:21 PDT 2016 (1468621821735)
      ... end of run
      INFO  [2016-07-15 15:30:25,410][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, service URL: /jndi/rmi://tableau.b-analytics.net:9400/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, service URL: /jndi/rmi://tableau.b-analytics.net:9400/jmxrmi
      INFO  [2016-07-15 15:30:55,657][main] (PerfRunHelper.java:225)   - Waiting for processes "Windows Perf Counter Data Retriever;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, service URL: /jndi/rmi://tableau.b-analytics.net:9400/jmxrmi
      INFO  [2016-07-15 15:31:25,876][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, service URL: /jndi/rmi://tableau.b-analytics.net:9400/jmxrmi
      INFO  [2016-07-15 15:31:56,173][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: vizqlserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:9401/jmxrmi
      INFO  [2016-07-15 15:32:26,469][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: vizqlserver#1, service URL: /jndi/rmi://tableau.b-analytics.net: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://tableau.b-analytics.net:9401/jmxrmi
      INFO  [2016-07-15 15:32:56,719][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: vizqlserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:9401/jmxrmi
      INFO  [2016-07-15 15:33:26,986][main] (PerfRunHelper.java:221)   - Timeout of Waiting for processes "JMX/Zabbix Counter Data Retriever" to complete. Killinng the processes.
      INFO  [2016-07-15 15:33:27,002][main] (PerfRunHelper.java:206)   - killing process JMX/Zabbix Counter Data Retriever
      INFO  [2016-07-15 15:33:27,006][main] (PerfRunHelper.java:208)   - Successfully killed process JMX/Zabbix Counter Data Retriever
      INFO  [2016-07-15 15:33:27,010][main] (PerfRunHelper.java:214)   - All processes have exited.
      INFO  [2016-07-15 15:33:27,014][main] (PerfRunMonitor.java:57)   - Perfrun is completed - ending monitor thread
      INFO  [2016-07-15 15:33:27,203][Thread-7] (JmeterResultDBSender.java:81)   - Finish processeing all Jmeter perf result samples.
      INFO  [2016-07-15 15:33:28,000][Thread-9] (PerfCounterDBSender.java:72)   - Finished processing all perf counter records
      Exception in thread "main" org.postgresql.util.PSQLException: ERROR: division by zero
        Where: SQL statement "UPDATE test_runs
                      SET TPS_average=(
                                   totalSamples/totalseconds
                               )
                      WHERE id=runId"
      PL/pgSQL function sp_update_test_run_stats(integer) line 116 at SQL statement
              at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2270)
              at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1998)
              at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
              at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:570)
              at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:420)
              at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:362)
              at com.tableausoftware.test.tools.ResultProcessor.PostgresDBHelper.updateTestRunStats(PostgresDBHelper.java:238)
              at com.tableausoftware.test.tools.ResultProcessor.ResultProcessor.signalRunCompleted(ResultProcessor.java:188)
              at com.tableausoftware.test.tools.perfRunHarness.Main.runOneTest(Main.java:261)
              at com.tableausoftware.test.tools.perfRunHarness.Main.main(Main.java:138)

      C:\tabjolt>

       

      I've done all recommended setting changes fromThe Mondo Tableau Server TabJolt Series – Part 3 - Tableau Love   and windows firewall is turned off

      • 473 Views
      • Tags:
        • 1. Re: Tabjolt - division by zero
          Obed Tsimi
          Obed Tsimi Employee Jul 18, 2016 11:58 AM (in response to Zach Krzyzanowski)

          Hello Zach,

           

          Thank you for reaching out. In order to better understand, when exactly (what point) do you get the output above? and what steps are taken prior and after prompted?

           

          Thanks

          • 2. Re: Tabjolt - division by zero
            Zach Krzyzanowski
            Zach Krzyzanowski Jul 19, 2016 10:34 AM (in response to Obed Tsimi)

            Hi Obed,

            I was able to resolve the original error by setting proxyEnabled to false in ServerTestConfig.yaml but now experience sporadic connection timeouts seen below.  This occurs when running Tabjolt with the following command: go --t=testplans\InteractVizLoadTest.jmx --d=60 --c=10

             

            I'm running Tabjolt on a virtual machine on my local laptop, separate from the Tableau server.  Neither the server or virtual machine are on a domain.  After the test completes, I am able to view some data, like KPI, but not others like VizQL results.

             

            C:\tabjolt>go --t=testplans\InteractVizLoadTest.jmx --d=60 --c=10
            [2016-07-19 13:03:35,807] Perf harness is started with parameters: --rootPath=C:\tabjolt --t=testplans\InteractVizLoadTest.jmx --d=60 --c=10
            [2016-07-19 13:03:36,026] Loading PerfTestConfig yaml file C:\tabjolt\config\PerfTestConfig.yaml
            [2016-07-19 13:03:36,182] Loading ServerTestConfig yaml file C:\tabjolt\config\ServerTestConfig.yaml
            -------------start collecting JMX counters--------------
            Output File:C:\tabjolt/results/2016-07-19_13-03-36/jmxcounter.tsv
            -------------start collecting Zabbix counters--------------
            Output File:C:\tabjolt/results/2016-07-19_13-03-36/zabbixcounter.tsv
            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://tableau.b-analytics.net:9400/jmxrmi
            INFO  [2016-07-19 13:04:06,714][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 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, service URL: /jndi/rmi://tableau.b-analytics.net:9400/jmxrmi
            Error   Unable to get instances for category Memory of host tableau.b-analytics.net. Skip collecting perf counters for the category. Exception Message: The network path was not found
            INFO  [2016-07-19 13:04:37,027][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 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, service URL: /jndi/rmi://tableau.b-analytics.net:9400/jmxrmi
            Error   Unable to get instances for category Processor of host tableau.b-analytics.net. Skip collecting perf counters for the category. Exception Message: The network path was not found
            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://tableau.b-analytics.net:9400/jmxrmi
            INFO  [2016-07-19 13:05:07,324][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 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: vizqlserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:9401/jmxrmi
            Error   Unable to get instances for category LogicalDisk of host tableau.b-analytics.net. Skip collecting perf counters for the category. Exception Message: The network path was not found
            INFO  [2016-07-19 13:05:37,573][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 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: vizqlserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:9401/jmxrmi
            Error   Unable to get instances for category Network Interface of host tableau.b-analytics.net. Skip collecting perf counters for the category. Exception Message: The network path was not found
            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://tableau.b-analytics.net:9401/jmxrmi
            INFO  [2016-07-19 13:06:07,870][main] (PerfRunHelper.java:162)   - Waiting for processes "Windows Perf Counter Data Retriever" to start. 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: vizqlserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:9401/jmxrmi
            INFO  [2016-07-19 13:06:38,151][main] (PerfRunHelper.java:158)   - Timeout of Waiting for processes "Windows Perf Counter Data Retriever" to start. Skip waiting for processes.
            INFO  [2016-07-19 13:06:38,166][main] (PerfRunHelper.java:346)   - -------------start Jmeter load test run-------------
            INFO  [2016-07-19 13:06:38,166][main] (PerfRunHelper.java:347)   - Output file: C:\tabjolt/results/2016-07-19_13-03-36/result-DESKTOP-RD85OP1-0.jtl
            INFO  [2016-07-19 13:06:38,182][main] (PerfRunHelper.java:348)   - Command: [C:\tabjolt/bin/jmeter.bat, , , , , , -n, -t=C:\tabjolt\testplans\InteractVizLoadTest.jmx, -j=C:\tabjolt/logs/jmeter_2016-07-19_13-03-36.log, -JthreadCount=10, -Jduration=60, -JloginWeight=1.0, -JconfigFolderPath=C:\tabjolt/config/, -Jlogpath=C:\tabjolt/results/2016-07-19_13-03-36/result-DESKTOP-RD85OP1-0.jtl, ]
            INFO  [2016-07-19 13:06:38,994][main] (ResultProcessor.java:132)   - -------------start processing perf counters and run result-------------
            INFO  [2016-07-19 13:06:39,057][main] (ResultProcessor.java:133)   - Perf run result is saving to result repository. Please use this RUN ID 38 to view your result in Tableau
            INFO  [2016-07-19 13:06:39,297][Thread-12] (PerfRunMonitor.java:37)   - Starting Perfrun monitor thread
            Error   Unable to get instances for category Process of host tableau.b-analytics.net. Skip collecting perf counters for the category. Exception Message: The network path was not found
            -------------start windows performance counters collection-------------
            Output File:c:\tabjolt/results/2016-07-19_13-03-36/wincounter.tsv
            Created the tree successfully using C:\tabjolt\testplans\InteractVizLoadTest.jmx
            Starting the test @ Tue Jul 19 13:06:41 PDT 2016 (1468958801089)
            Waiting for possible shutdown message on port 4445
            SLF4J: Class path contains multiple SLF4J bindings.
            SLF4J: Found binding in [jar:file:/C:/tabjolt/lib/slf4j-nop-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
            SLF4J: Found binding in [jar:file:/C:/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]
            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://tableau.b-analytics.net:10000/jmxrmi
            #0      Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 1762 Errors: 1
            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://tableau.b-analytics.net:10000/jmxrmi
            #19     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 2074 Errors: 1
            #20     Threads: 10/10  Samples: 6      Latency: 0      Resp.Time: 20315        Errors: 0
            #21     Threads: 10/10  Samples: 4      Latency: 0      Resp.Time: 16423        Errors: 1
            #27     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 22345        Errors: 0
            #28     Threads: 10/10  Samples: 2      Latency: 0      Resp.Time: 7180 Errors: 0
            #29     Threads: 10/10  Samples: 5      Latency: 0      Resp.Time: 8326 Errors: 0
            #30     Threads: 10/10  Samples: 5      Latency: 0      Resp.Time: 4255 Errors: 3
            #34     Threads: 10/10  Samples: 2      Latency: 0      Resp.Time: 4727 Errors: 1
            #36     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 7512 Errors: 0
            #37     Threads: 10/10  Samples: 4      Latency: 0      Resp.Time: 7955 Errors: 0
            #38     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 9355 Errors: 0
            #39     Threads: 10/10  Samples: 2      Latency: 0      Resp.Time: 9176 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: dataserver, service URL: /jndi/rmi://tableau.b-analytics.net:10000/jmxrmi
            #40     Threads: 10/10  Samples: 2      Latency: 0      Resp.Time: 9406 Errors: 1
            #41     Threads: 10/10  Samples: 2      Latency: 0      Resp.Time: 1200 Errors: 2
            #42     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 302  Errors: 1
            #43     Threads: 10/10  Samples: 3      Latency: 0      Resp.Time: 4625 Errors: 1
            #46     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 7433 Errors: 0
            #47     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 7979 Errors: 0
            #50     Threads: 10/10  Samples: 5      Latency: 0      Resp.Time: 8100 Errors: 3
            #51     Threads: 10/10  Samples: 4      Latency: 0      Resp.Time: 9242 Errors: 2
            #52     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 1125 Errors: 1
            #53     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 8855 Errors: 1
            #54     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 6431 Errors: 0
            #55     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 7683 Errors: 0
            #56     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 370  Errors: 1
            #57     Threads: 10/10  Samples: 2      Latency: 0      Resp.Time: 4692 Errors: 2
            #58     Threads: 10/10  Samples: 1      Latency: 0      Resp.Time: 9414 Errors: 0
            #59     Threads: 9/10   Samples: 3      Latency: 0      Resp.Time: 8322 Errors: 1
            #60     Threads: 7/10   Samples: 2      Latency: 0      Resp.Time: 7643 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: dataserver, service URL: /jndi/rmi://tableau.b-analytics.net:10000/jmxrmi
            #61     Threads: 5/10   Samples: 2      Latency: 0      Resp.Time: 8189 Errors: 1
            #62     Threads: 4/10   Samples: 1      Latency: 0      Resp.Time: 6349 Errors: 0
            #63     Threads: 3/10   Samples: 1      Latency: 0      Resp.Time: 5819 Errors: 0
            Tidying up ...    @ Tue Jul 19 13:07:52 PDT 2016 (1468958872729)
            ... end of run
            INFO  [2016-07-19 13:08:00,292][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: dataserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:10001/jmxrmi
            INFO  [2016-07-19 13:08:30,620][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: dataserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:10001/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#1, service URL: /jndi/rmi://tableau.b-analytics.net:10001/jmxrmi
            INFO  [2016-07-19 13:09:00,916][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: dataserver#1, service URL: /jndi/rmi://tableau.b-analytics.net:10001/jmxrmi
            INFO  [2016-07-19 13:09:31,229][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: vizportal, service URL: /jndi/rmi://tableau.b-analytics.net:8900/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: vizportal, service URL: /jndi/rmi://tableau.b-analytics.net:8900/jmxrmi
            INFO  [2016-07-19 13:10:01,541][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: vizportal, service URL: /jndi/rmi://tableau.b-analytics.net:8900/jmxrmi
            INFO  [2016-07-19 13:10:31,854][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: vizportal, service URL: /jndi/rmi://tableau.b-analytics.net:8900/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, service URL: /jndi/rmi://tableau.b-analytics.net:9400/jmxrmi
            INFO  [2016-07-19 13:11:02,136][main] (PerfRunHelper.java:221)   - Timeout of Waiting for processes "JMX/Zabbix Counter Data Retriever" to complete. Killinng the processes.
            INFO  [2016-07-19 13:11:02,136][main] (PerfRunHelper.java:206)   - killing process JMX/Zabbix Counter Data Retriever
            INFO  [2016-07-19 13:11:02,136][main] (PerfRunHelper.java:208)   - Successfully killed process JMX/Zabbix Counter Data Retriever
            INFO  [2016-07-19 13:11:02,136][main] (PerfRunHelper.java:214)   - All processes have exited.
            INFO  [2016-07-19 13:11:02,151][main] (PerfRunMonitor.java:57)   - Perfrun is completed - ending monitor thread
            INFO  [2016-07-19 13:11:02,995][Thread-9] (PerfCounterDBSender.java:72)   - Finished processing all perf counter records
            INFO  [2016-07-19 13:11:03,697][Thread-7] (JmeterResultDBSender.java:81)   - Finish processeing all Jmeter perf result samples.
            INFO  [2016-07-19 13:11:03,760][main] (ResultProcessor.java:190)   - -----------------------------------------------------
            INFO  [2016-07-19 13:11:03,760][main] (ResultProcessor.java:191)   - Perf run result have been stored. Please use this RUN ID 38 to view your result in Tableau

            C:\tabjolt>

            • 3. Re: Tabjolt - division by zero
              Obed Tsimi
              Obed Tsimi Employee Jul 20, 2016 9:47 AM (in response to Zach Krzyzanowski)

              Hey Zach,

               

              Thanks for the info. This will need further analysis. Could it be possible to open a support ticket with our support team? It could be a little tricky since it's sporadic.

               

              Cheers

              • 4. Re: Tabjolt - division by zero
                Obed Tsimi
                Obed Tsimi Employee Jul 21, 2016 11:00 AM (in response to Zach Krzyzanowski)

                Zach,

                 

                I might have given you some misleading information. This issue falls outside the scope of Tableau Support actually, and the forum here might be the best way to keep seeking assistance on this issue. I will also try to review and find more resources to assist with this.

                 

                Thanks

                • 5. Re: Tabjolt - division by zero
                  Russell Christopher
                  Russell Christopher Jul 23, 2016 11:41 PM (in response to Zach Krzyzanowski)

                  You have a bunch of stuff going on here

                   

                  Messages like this (referring to any number of difference services)...

                   

                  The Health Service failed to open JMX connection with component: vizqlserver, service URL: /jndi/rmi://tableau.b-analytics.net:9400/jmxrmi

                   

                  ...generally mean one (or more) of a couple things. In descending order of likelihood:

                   

                  • JMX hasn't been enabled on Tableau Server
                  • You have a firewall blocking ports mentioned
                  • You have bad network connectivity

                   

                  Messages like this (referring to any perfomon counter)....

                   

                  Error   Unable to get instances for category Processor of host tableau.b-analytics.net. Skip collecting perf counters for the category. Exception Message: The network path was not found

                   

                  ...generally mean one (or more) of a couple things. In descending order of likelihood:

                   

                  • The account that you're logged in at the console with and running TabJolt with doesn't have permissions to to connect to the Windows Server and collect perfmon data
                  • The Windows Server Tableau is installed on hasn't been configured to allow remote collection of perfmon stats
                  • File Sharing is not enabled and/or Firewalls are blocking attempts to connect

                   

                  When you see errors like this:

                   

                  #34     Threads: 10/10  Samples: 2      Latency: 0      Resp.Time: 4727 Errors: 1

                   

                  ...it could mean any of the following:

                   

                  • The URL for one or more of the vizzes in your vizpool.csv file is wrong - therefore when we make a request against it, it fails
                  • TabJolt itself can't interpret the response coming from Tableau Server - the viz rendered fine, but TabJolt gets confused and throws an error.  (to test either this scenario or the previous one, select a SINGLE known "good" viz string" and test ONLY that single worksheet)

                   

                  Because you're currently not collecting any information from Tableau Server itself (the first error I pasted in) OR Perfmon Information from Windows Server (the second error message), only the basic dashboards will function for you - no data exists for anything related to processes, etc.

                   

                  You mention "experience sporadic connection timeouts seen below."  and I think you're keying on the the "Connection Timed Out" messages. These aren't sporadic - you're not connecting at all.

                   

                  So, at the highest level, I suspect you've just forgotten to do a few housekeeping things, and those lapses are causing most of the problems you're seeing here. A good guide that covers most of the errors that folks new to TabJolt make can be found here:

                   

                  The Mondo Tableau Server TabJolt Post Series - Part 1 - Tableau Love

                   

                  The Mondo Tableau Server TabJolt Series - Part 2 - Tableau Love

                   

                  The Mondo Tableau Server TabJolt Series – Part 3 - Tableau Love

                   

                  Some of the stuff mentioned above (specifics around the config files) have changed with the newest release of TabJolt, but you really need the basic troubleshooting steps. Looks like your config files (above and beyond the potential for "bad" URLS pointing to your vizzes) are probably pretty good otherwise you wouldn't have gotten as far as you already have....