3 Replies Latest reply on Dec 8, 2017 1:37 AM by Lénaïc Riédinger

    Tabjolt Read Timed Out - Error with the Testplan

    Eric Liong

      Hi all,

       

      Weird situation. Finally got Tabjolt running smoothly when I decided to try the customized test plans in Tabjolt\Testplans\CustomizedTestPlan specifically the Stepup test.

      After making seemingly any edit to the JMX file in jMeter in the "InteractVizStepupThreadGroup" would result in the following. 

       

      "Failed to connect to the JMX connector due to the following error: SocketTimeout

      Exception: Read timed out"

       

      I did try including "<name>saveConfig</name>" as they mentioned inside the Tabjolt Install Guide and that made no difference. After a few interfaces between my head and my desk I used WinMerge to compare and remove this block of code.

                    <elementProp name="CustomParams" elementType="Argument">

                      <stringProp name="Argument.name">CustomParams</stringProp>

                      <stringProp name="Argument.value">${CustomParams}</stringProp>

                      <stringProp name="Argument.metadata">=</stringProp>

                    </elementProp>

      Now my Tabjolt tests seem to be running correctly again. Why did this work? Is this "Correct"? Has anyone else experienced this?

      To recap: My Tabjolt ran successfully using the default Testplans and even the original files under "CustomizedTestPlan".

      Editing the JMX files in JMeter caused them to all fail. The edits I was making were simple things like number of threads, time between ramp ups and the holding period. (See screenshot)

       

       

       

       

       

       

      Logs from the run:

       

      C:\Tabjolt>go --t=testplans\customizedtestplan\interactvizloadtest_stepuppattern

      .jmx --d=660 --c=1

      [2017-12-05 13:41:56,095] Perf harness is started with parameters: --rootPath=C:

      \Tabjolt --t=testplans\customizedtestplan\interactvizloadtest_stepuppattern.jmx

      --d=660 --c=1

      [2017-12-05 13:41:56,197] Loading PerfTestConfig yaml file C:\Tabjolt\config\Per

      fTestConfig.yaml

      [2017-12-05 13:41:56,253] Loading ServerTestConfig yaml file C:\Tabjolt\config\S

      erverTestConfig.yaml

      INFO  [2017-12-05 13:41:56,384][main] (PerfRunHelper.java:247)   - C:\Tabjolt\bi

      n\dataretriever.exe -configpath=C:\Tabjolt\config\dataretriever.config -duration

      =660 -outputpath=C:\Tabjolt\results\2017-12-05_13-41-56\wincounter.tsv

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

      Output File:C:\Tabjolt/results/2017-12-05_13-41-56/jmxcounter.tsv

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

      Output File:C:\Tabjolt/results/2017-12-05_13-41-56/zabbixcounter.tsv

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

      Output File:c:\tabjolt\results\2017-12-05_13-41-56\wincounter.tsv

      INFO  [2017-12-05 13:42:07,401][main] (PerfRunHelper.java:351)   - -------------

      start Jmeter load test run-------------

      INFO  [2017-12-05 13:42:07,402][main] (PerfRunHelper.java:352)   - Output file:

      C:\Tabjolt/results/2017-12-05_13-41-56/result-M379932-0.jtl

      INFO  [2017-12-05 13:42:07,403][main] (PerfRunHelper.java:353)   - Command: [C:\

      Tabjolt/bin/jmeter.bat, , , , , , -n, -t=C:\Tabjolt\testplans\customizedtestplan

      \interactvizloadtest_stepuppattern.jmx, -j=C:\Tabjolt/logs/jmeter_2017-12-05_13-

      41-56.log, -JthreadCount=1, -Jduration=660, -JloginWeight=1.0, -JconfigFolderPat

      h=C:\Tabjolt/config/, -Jlogpath=C:\Tabjolt/results/2017-12-05_13-41-56/result-M3

      79932-0.jtl, , ]

      INFO  [2017-12-05 13:42:07,523][main] (ResultProcessor.java:129)   - -----------

      --start processing perf counters and run result-------------

      INFO  [2017-12-05 13:42:07,525][main] (ResultProcessor.java:130)   - Perf run re

      sult is saving to result repository. Please use this RUN ID 14 to view your resu

      lt in Tableau

      INFO  [2017-12-05 13:42:07,542][Thread-7] (PerfRunMonitor.java:37)   - Starting

      Perfrun monitor thread

      Created the tree successfully using C:\Tabjolt\testplans\customizedtestplan\inte

      ractvizloadtest_stepuppattern.jmx

      Starting the test @ Tue Dec 05 13:42:07 MST 2017 (1512506527820)

      Waiting for possible shutdown message on port 4445

      FATAL [2017-12-05 13:42:08,117][setUp Thread Group 1-1] (LoadSessionSetup.java:7

      8)   - Failed to set up load test session. Stopping the test run.

      java.lang.NullPointerException

              at com.tableausoftware.test.server.perfTestSuite.LoadSessionSetup.runTes

      t(LoadSessionSetup.java:52)

              at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSample

      r.java:191)

              at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.j

      ava:429)

              at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:257)

              at java.lang.Thread.run(Thread.java:745)

      Tidying up ...    @ Tue Dec 05 13:42:08 MST 2017 (1512506528152)

      ... end of run

      INFO  [2017-12-05 13:42:27,543][main] (PerfRunHelper.java:193)   - Jmeter proces

      s has exited. Waiting for the other processes to exit.

      Failed to connect to the JMX connector due to the following error: SocketTimeout

      Exception: Read timed out

      Failed to get the object from the pool due to the following error: SocketTimeout

      Exception: Read timed out

      The Health Service failed to open JMX connection with component: vizqlserver, se

      rvice URL: /jndi/rmi://WSTABLEAU02:9400/jmxrmi

      INFO  [2017-12-05 13:42:57,555][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 30 seconds have elapsed.

      INFO  [2017-12-05 13:43:27,559][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 60 seconds have elapsed.

      Failed to connect to the JMX connector due to the following error: SocketTimeout

      Exception: Read timed out

      Failed to get the object from the pool due to the following error: SocketTimeout

      Exception: Read timed out

      The Health Service failed to open JMX connection with component: vizqlserver, se

      rvice URL: /jndi/rmi://WSTABLEAU02:9400/jmxrmi

      INFO  [2017-12-05 13:43:57,567][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 90 seconds have elapsed.

      INFO  [2017-12-05 13:44:27,574][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 120 seconds have elapsed.

      Failed to connect to the JMX connector due to the following error: SocketTimeout

      Exception: Read timed out

      Failed to get the object from the pool due to the following error: SocketTimeout

      Exception: Read timed out

      The Health Service failed to open JMX connection with component: vizqlserver, se

      rvice URL: /jndi/rmi://WSTABLEAU02:9400/jmxrmi

      INFO  [2017-12-05 13:44:57,578][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 150 seconds have elapsed.

      INFO  [2017-12-05 13:45:27,582][main] (PerfRunHelper.java:219)   - Timeout of Wa

      iting for processes "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data

      Retriever" to complete. Killinng the processes.

      INFO  [2017-12-05 13:45:27,583][main] (PerfRunHelper.java:204)   - killing proce

      ss Windows Perf Counter Data Retriever

      INFO  [2017-12-05 13:45:27,585][main] (PerfRunHelper.java:206)   - Successfully

      killed process Windows Perf Counter Data Retriever

      INFO  [2017-12-05 13:45:27,586][main] (PerfRunHelper.java:204)   - killing proce

      ss JMX/Zabbix Counter Data Retriever

      INFO  [2017-12-05 13:45:27,587][main] (PerfRunHelper.java:206)   - Successfully

      killed process JMX/Zabbix Counter Data Retriever

      INFO  [2017-12-05 13:45:27,590][main] (PerfRunHelper.java:212)   - All processes

      have exited.

      INFO  [2017-12-05 13:45:27,591][main] (PerfRunMonitor.java:57)   - Perfrun is co

      mpleted - ending monitor thread

      INFO  [2017-12-05 13:45:28,670][Thread-3] (PerfCounterDBSender.java:72)   - Fini

      shed processing all perf counter records

      INFO  [2017-12-05 13:45:28,686][Thread-1] (JmeterResultDBSender.java:81)   - Fin

      ish processeing all Jmeter perf result samples.

      INFO  [2017-12-05 13:45:28,713][main] (ResultProcessor.java:186)   - -----------

      ------------------------------------------

      INFO  [2017-12-05 13:45:28,715][main] (ResultProcessor.java:187)   - Perf run re

      sult have been stored. Please use this RUN ID 14 to view your result in Tableau

       

       

      C:\Tabjolt>

       

       

      Logs from the Verbose Run:

       

      C:\Tabjolt>go --t=testplans\customizedtestplan\interactvizloadtest_stepuppattern

      .jmx --d=660 --c=1

      [2017-12-06 11:03:15,976] Perf harness is started with parameters: --rootPath=C:

      \Tabjolt --t=testplans\customizedtestplan\interactvizloadtest_stepuppattern.jmx

      --d=660 --c=1

      [2017-12-06 11:03:16,068] Loading PerfTestConfig yaml file C:\Tabjolt\config\Per

      fTestConfig.yaml

      [2017-12-06 11:03:16,122] Loading ServerTestConfig yaml file C:\Tabjolt\config\S

      erverTestConfig.yaml

      DEBUG [2017-12-06 11:03:16,134][main] (AbstractConfig.java:279)   - Looking for

      config file: log4j.properties

      DEBUG [2017-12-06 11:03:16,135][main] (AbstractConfig.java:296)   - Looking for

      specific folder named [config] in tree of [C:\Tabjolt\lib\ext]

      DEBUG [2017-12-06 11:03:16,139][main] (AbstractConfig.java:329)   - Found config

      file 'log4j.properties' for class class com.tableausoftware.test.server.configu

      ration.ServerTestConfig at '/C:/Tabjolt/config/log4j.properties'

      DEBUG [2017-12-06 11:03:16,141][main] (ServerTestConfig.java:97)   - Loading Ser

      verTestConfig from: ServerTestConfig.yaml

      DEBUG [2017-12-06 11:03:16,142][main] (AbstractConfig.java:108)   - Read system

      property java.test.config.override=null

      DEBUG [2017-12-06 11:03:16,142][main] (AbstractConfig.java:112)   - Using test c

      onfig Override 'null'

      DEBUG [2017-12-06 11:03:16,143][main] (AbstractConfig.java:95)   - No override i

      s set, using default

      DEBUG [2017-12-06 11:03:16,143][main] (AbstractConfig.java:279)   - Looking for

      config file: ServerTestConfig.yaml

      DEBUG [2017-12-06 11:03:16,144][main] (AbstractConfig.java:296)   - Looking for

      specific folder named [config] in tree of [C:\Tabjolt\lib\ext]

      DEBUG [2017-12-06 11:03:16,148][main] (AbstractConfig.java:329)   - Found config

      file 'ServerTestConfig.yaml' for class class com.tableausoftware.test.server.co

      nfiguration.ServerTestConfig at '/C:/Tabjolt/config/ServerTestConfig.yaml'

      DEBUG [2017-12-06 11:03:16,148][main] (AbstractConfig.java:144)   - Loading conf

      ig [class com.tableausoftware.test.server.configuration.ServerTestConfig] from [

      ServerTestConfig.yaml]

      DEBUG [2017-12-06 11:03:16,149][main] (AbstractConfig.java:148)   - Found config

      [default]

      DEBUG [2017-12-06 11:03:16,165][main] (AbstractConfig.java:158)   - Completed re

      ading the [default] config

      INFO  [2017-12-06 11:03:16,252][main] (PerfRunHelper.java:247)   - C:\Tabjolt\bi

      n\dataretriever.exe -configpath=C:\Tabjolt\config\dataretriever.config -duration

      =660 -outputpath=C:\Tabjolt\results\2017-12-06_11-03-16\wincounter.tsv

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

      Output File:C:\Tabjolt/results/2017-12-06_11-03-16/jmxcounter.tsv

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

      Output File:C:\Tabjolt/results/2017-12-06_11-03-16/zabbixcounter.tsv

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

      Output File:c:\tabjolt\results\2017-12-06_11-03-16\wincounter.tsv

      INFO  [2017-12-06 11:03:25,268][main] (PerfRunHelper.java:351)   - -------------

      start Jmeter load test run-------------

      INFO  [2017-12-06 11:03:25,269][main] (PerfRunHelper.java:352)   - Output file:

      C:\Tabjolt/results/2017-12-06_11-03-16/result-M379932-0.jtl

      INFO  [2017-12-06 11:03:25,270][main] (PerfRunHelper.java:353)   - Command: [C:\

      Tabjolt/bin/jmeter.bat, , , , , , -n, -t=C:\Tabjolt\testplans\customizedtestplan

      \interactvizloadtest_stepuppattern.jmx, -j=C:\Tabjolt/logs/jmeter_2017-12-06_11-

      03-16.log, -JthreadCount=1, -Jduration=660, -JloginWeight=1.0, -JconfigFolderPat

      h=C:\Tabjolt/config/, -Jlogpath=C:\Tabjolt/results/2017-12-06_11-03-16/result-M3

      79932-0.jtl, , ]

      INFO  [2017-12-06 11:03:25,386][main] (ResultProcessor.java:129)   - -----------

      --start processing perf counters and run result-------------

      INFO  [2017-12-06 11:03:25,388][main] (ResultProcessor.java:130)   - Perf run re

      sult is saving to result repository. Please use this RUN ID 17 to view your resu

      lt in Tableau

      INFO  [2017-12-06 11:03:25,405][Thread-7] (PerfRunMonitor.java:37)   - Starting

      Perfrun monitor thread

      Created the tree successfully using C:\Tabjolt\testplans\customizedtestplan\inte

      ractvizloadtest_stepuppattern.jmx

      Starting the test @ Wed Dec 06 11:03:25 MST 2017 (1512583405721)

      Waiting for possible shutdown message on port 4445

      DEBUG [2017-12-06 11:03:25,937][setUp Thread Group 1-1] (AbstractConfig.java:279

      )   - Looking for config file: log4j.properties

      DEBUG [2017-12-06 11:03:25,938][setUp Thread Group 1-1] (AbstractConfig.java:296

      )   - Looking for specific folder named [config] in tree of [C:\Tabjolt\lib\ext]

       

       

      DEBUG [2017-12-06 11:03:25,942][setUp Thread Group 1-1] (AbstractConfig.java:329

      )   - Found config file 'log4j.properties' for class class com.tableausoftware.t

      est.server.configuration.ServerTestConfig at '/C:/Tabjolt/config/log4j.propertie

      s'

      DEBUG [2017-12-06 11:03:25,943][setUp Thread Group 1-1] (ServerTestConfig.java:9

      7)   - Loading ServerTestConfig from: ServerTestConfig.yaml

      DEBUG [2017-12-06 11:03:25,943][setUp Thread Group 1-1] (AbstractConfig.java:108

      )   - Read system property java.test.config.override=null

      DEBUG [2017-12-06 11:03:25,944][setUp Thread Group 1-1] (AbstractConfig.java:112

      )   - Using test config Override 'null'

      DEBUG [2017-12-06 11:03:25,944][setUp Thread Group 1-1] (AbstractConfig.java:95)

         - No override is set, using default

      DEBUG [2017-12-06 11:03:25,944][setUp Thread Group 1-1] (AbstractConfig.java:279

      )   - Looking for config file: ServerTestConfig.yaml

      DEBUG [2017-12-06 11:03:25,944][setUp Thread Group 1-1] (AbstractConfig.java:296

      )   - Looking for specific folder named [config] in tree of [C:\Tabjolt\lib\ext]

       

       

      DEBUG [2017-12-06 11:03:25,947][setUp Thread Group 1-1] (AbstractConfig.java:329

      )   - Found config file 'ServerTestConfig.yaml' for class class com.tableausoftw

      are.test.server.configuration.ServerTestConfig at '/C:/Tabjolt/config/ServerTest

      Config.yaml'

      DEBUG [2017-12-06 11:03:25,948][setUp Thread Group 1-1] (AbstractConfig.java:144

      )   - Loading config [class com.tableausoftware.test.server.configuration.Server

      TestConfig] from [ServerTestConfig.yaml]

      DEBUG [2017-12-06 11:03:25,949][setUp Thread Group 1-1] (AbstractConfig.java:148

      )   - Found config [default]

      DEBUG [2017-12-06 11:03:26,006][setUp Thread Group 1-1] (AbstractConfig.java:158

      )   - Completed reading the [default] config

      DEBUG [2017-12-06 11:03:26,006][setUp Thread Group 1-1] (AbstractConfig.java:279

      )   - Looking for config file: log4j.properties

      DEBUG [2017-12-06 11:03:26,006][setUp Thread Group 1-1] (AbstractConfig.java:296

      )   - Looking for specific folder named [config] in tree of [C:\Tabjolt\lib\ext]

       

       

      DEBUG [2017-12-06 11:03:26,010][setUp Thread Group 1-1] (AbstractConfig.java:329

      )   - Found config file 'log4j.properties' for class class com.tableausoftware.t

      est.server.configuration.ServerTestConfig at '/C:/Tabjolt/config/log4j.propertie

      s'

      DEBUG [2017-12-06 11:03:26,012][setUp Thread Group 1-1] (ServerTestConfig.java:9

      7)   - Loading ServerTestConfig from: C:\Tabjolt\config\ServerTestConfig.yaml

      DEBUG [2017-12-06 11:03:26,012][setUp Thread Group 1-1] (AbstractConfig.java:108

      )   - Read system property java.test.config.override=null

      DEBUG [2017-12-06 11:03:26,012][setUp Thread Group 1-1] (AbstractConfig.java:112

      )   - Using test config Override 'null'

      DEBUG [2017-12-06 11:03:26,012][setUp Thread Group 1-1] (AbstractConfig.java:95)

         - No override is set, using default

      DEBUG [2017-12-06 11:03:26,012][setUp Thread Group 1-1] (AbstractConfig.java:144

      )   - Loading config [class com.tableausoftware.test.server.configuration.Server

      TestConfig] from [C:\Tabjolt\config\ServerTestConfig.yaml]

      DEBUG [2017-12-06 11:03:26,012][setUp Thread Group 1-1] (AbstractConfig.java:148

      )   - Found config [default]

      DEBUG [2017-12-06 11:03:26,014][setUp Thread Group 1-1] (AbstractConfig.java:158

      )   - Completed reading the [default] config

      DEBUG [2017-12-06 11:03:26,015][setUp Thread Group 1-1] (AbstractConfig.java:108

      )   - Read system property java.test.config.override=null

      DEBUG [2017-12-06 11:03:26,015][setUp Thread Group 1-1] (AbstractConfig.java:112

      )   - Using test config Override 'null'

      DEBUG [2017-12-06 11:03:26,015][setUp Thread Group 1-1] (AbstractConfig.java:95)

         - No override is set, using default

      DEBUG [2017-12-06 11:03:26,016][setUp Thread Group 1-1] (AbstractConfig.java:144

      )   - Loading config [class com.tableausoftware.test.server.perfLib.PerfTestConf

      ig] from [C:\Tabjolt\config\PerfTestConfig.yaml]

      DEBUG [2017-12-06 11:03:26,018][setUp Thread Group 1-1] (AbstractConfig.java:148

      )   - Found config [default]

      DEBUG [2017-12-06 11:03:26,022][setUp Thread Group 1-1] (AbstractConfig.java:158

      )   - Completed reading the [default] config

      DEBUG [2017-12-06 11:03:26,023][setUp Thread Group 1-1] (LoadSessionSetup.java:5

      0)   - Custom params string: ${CustomParams}

      FATAL [2017-12-06 11:03:26,023][setUp Thread Group 1-1] (LoadSessionSetup.java:7

      8)   - Failed to set up load test session. Stopping the test run.

      java.lang.NullPointerException

              at com.tableausoftware.test.server.perfTestSuite.LoadSessionSetup.runTes

      t(LoadSessionSetup.java:52)

              at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSample

      r.java:191)

              at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.j

      ava:429)

              at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:257)

              at java.lang.Thread.run(Thread.java:745)

      Tidying up ...    @ Wed Dec 06 11:03:26 MST 2017 (1512583406054)

      ... end of run

      INFO  [2017-12-06 11:03:45,406][main] (PerfRunHelper.java:193)   - Jmeter proces

      s has exited. Waiting for the other processes to exit.

      INFO  [2017-12-06 11:04:15,410][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 30 seconds have elapsed.

      INFO  [2017-12-06 11:04:55,788][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 60 seconds have elapsed.

      INFO  [2017-12-06 11:05:25,792][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 90 seconds have elapsed.

      INFO  [2017-12-06 11:05:55,796][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 120 seconds have elapsed.

      INFO  [2017-12-06 11:06:25,800][main] (PerfRunHelper.java:223)   - Waiting for p

      rocesses "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data Retriever"

      to complete. 150 seconds have elapsed.

      INFO  [2017-12-06 11:06:55,804][main] (PerfRunHelper.java:219)   - Timeout of Wa

      iting for processes "Windows Perf Counter Data Retriever;JMX/Zabbix Counter Data

      Retriever" to complete. Killinng the processes.

      INFO  [2017-12-06 11:06:55,805][main] (PerfRunHelper.java:204)   - killing proce

      ss Windows Perf Counter Data Retriever

      INFO  [2017-12-06 11:06:55,806][main] (PerfRunHelper.java:206)   - Successfully

      killed process Windows Perf Counter Data Retriever

      INFO  [2017-12-06 11:06:55,807][main] (PerfRunHelper.java:204)   - killing proce

      ss JMX/Zabbix Counter Data Retriever

      INFO  [2017-12-06 11:06:55,808][main] (PerfRunHelper.java:206)   - Successfully

      killed process JMX/Zabbix Counter Data Retriever

      INFO  [2017-12-06 11:06:55,809][main] (PerfRunHelper.java:212)   - All processes

      have exited.

      INFO  [2017-12-06 11:06:55,809][main] (PerfRunMonitor.java:57)   - Perfrun is co

      mpleted - ending monitor thread

      INFO  [2017-12-06 11:06:56,532][Thread-1] (JmeterResultDBSender.java:81)   - Fin

      ish processeing all Jmeter perf result samples.

      INFO  [2017-12-06 11:06:56,537][Thread-3] (PerfCounterDBSender.java:72)   - Fini

      shed 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(QueryEx

      ecutorImpl.java:2157)

              at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutor

      Impl.java:1886)

              at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.ja

      va:255)

              at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Stat

      ement.java:555)

              at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(Abstract

      Jdbc2Statement.java:417)

              at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdb

      c2Statement.java:359)

              at com.tableausoftware.test.tools.ResultProcessor.PostgresDBHelper.updat

      eTestRunStats(PostgresDBHelper.java:240)

              at com.tableausoftware.test.tools.ResultProcessor.ResultProcessor.signal

      RunCompleted(ResultProcessor.java:184)

              at com.tableausoftware.test.tools.perfRunHarness.Main.runOneTest(Main.ja

      va:254)

              at com.tableausoftware.test.tools.perfRunHarness.Main.main(Main.java:140

      )

       

       

      C:\Tabjolt>