Jmeter scripts that use Ultimate Thread Group are not running on Taurus

[abbya...@gmail.com]

Hi there,

I have a JMeter script that uses the Ultimate Thread Group plugin. Running it directly from JMeter is fine but when I try to run the exact same script on Taurus, the run completes without executing a single test. 

Other plugins like the Stepping Thread Group runs without any issues.

Can you please help?

Thank you.

[Andrey Pokhilko]

That seems to be a bug. We'll try to fix it asap.

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/687611a9-7e9b-428b-90d8-3138157aab1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ta...@blazemeter.com]

Hi.
I can't reproduce your bug, Ultimate Tread Group works well with Taurus at me.
Show your jmx and taurus config please.

[Abby Adegun]

I did not set up the Taurus on our server and I'm quite junior to Linux so I'm not sure how to check the config. Can you please point me to the right direction.

Also attached is the jmx file used.

Thanks.

[ta...@blazemeter.com]

Your jmx doesn't contain any information about treads (in JMeter GUI: Test_Plan > Ultimate_Thread_Group > Treads_Schedule) so this script can't work anyway.

[ta...@blazemeter.com]

As you need to say Taurus about load size, next simple yaml config may be useful:

---

execution:

- concurrency: 5

  ramp-up: 20

  scenario:

    script: <path_to_your_script>/exampleUltimateThread.jmx

[abbya...@gmail.com]

Here's a screenshot of the schedule I set up for my script. It was done directly on JMeter as opposed to a yml. I'm not sure why it doesn't show on your side.

And here is the schedule from my jmx file:

<collectionProp name="threads_schedule">

          <collectionProp name="-388461159">

            <stringProp name="49">1</stringProp>

            <stringProp name="48">0</stringProp>

            <stringProp name="53">5</stringProp>

            <stringProp name="53">5</stringProp>

            <stringProp name="53">5</stringProp>

          </collectionProp>

          <collectionProp name="-1506270414">

            <stringProp name="49">1</stringProp>

            <stringProp name="1574">17</stringProp>

            <stringProp name="53">5</stringProp>

            <stringProp name="53">5</stringProp>

            <stringProp name="53">5</stringProp>

          </collectionProp>

        </collectionProp>

[abbya...@gmail.com]

And the following yml was generated after calling :

 bzt scripts/exampleUltimateThread.jmx -v -o modules.jmeter.path=/apache-jmeter-2.13/bin/jmeter.sh

(Apologies for the copy-paste, but for some reason I no longer have the option to attach a file)

---

cli-aliases:

  gui:

    modules:

      jmeter:

        gui: true

  locations:

    modules:

      cloud:

        dump-locations: true

    provisioning: cloud

  report:

    reporting:

    - blazemeter

execution:

- concurrency:

    local: null

  distributed: []

  executor: jmeter

  hold-for: 0

  iterations: null

  ramp-up: null

  scenario:

    data-sources: {}

    disable-listeners: true

    modifications: {}

    properties:

      jmeter.save.saveservice.timestamp_format: ms

      jmeterengine.nongui.maxport: 4445

      jmeterengine.nongui.port: 4445

    requests: {}

    script: scripts/exampleUltimateThread.jmx

    variables: {}

  steps: null

  throughput:

    local: null

  write-xml-jtl: error

included-configs: []

install-id: 2d92cf4d-0135-4668-bd03-c4f62ca7b4d7

modules:

  blazemeter:

    class: bzt.modules.blazemeter.BlazeMeterUploader

  cloud:

    class: bzt.modules.blazemeter.CloudProvisioning

  console:

    class: bzt.modules.console.ConsoleStatusReporter

    disable: false

  consolidator:

    buffer-seconds: 2

    class: bzt.modules.aggregator.ConsolidatingAggregator

    generalize-labels: false

    ignore-labels:

    - ignore

    percentiles:

    - 0.0

    - 50.0

    - 90.0

    - 95.0

    - 99.0

    - 99.9

    - 100.0

  fail-criteria:

    class: bzt.modules.passfail.PassFailStatus

  final_stats:

    class: bzt.modules.reporting.FinalStatus

  gatling:

    class: bzt.modules.gatling.GatlingExecutor

  grinder:

    class: bzt.modules.grinder.GrinderExecutor

    path: ~/.bzt/grinder-taurus/lib/grinder.jar

    properties:

      grinder.useConsole: false

  jmeter:

    class: bzt.modules.jmeter.JMeterExecutor

    gui: false

    path: /home/ec2-user/Jmeter/apache-jmeter-2.13/bin/jmeter.sh

    plugins-download-link: http://jmeter-plugins.org/files/JMeterPlugins-{plugin}-1.3.1.zip

    properties:

      jmeter.save.saveservice.autoflush: 'true'

      jmeter.save.saveservice.connect_time: 'true'

      jmeter.save.saveservice.timestamp_format: ms

      jmeterengine.force.system.exit: 'true'

      jmeterengine.nongui.maxport: 4445

      jmeterengine.nongui.port: 4445

      mode: Stripped

      summariser.name: ''

      user.classpath: /<path_to_class>

    rename-distributed-threads: true

    shutdown-port: 4445

    shutdown-wait: 5

    system-properties: {}

    version: '2.13'

  jtl-loader: bzt.modules.jmeter.JMeterJTLLoaderExecutor

  junit-xml:

    class: bzt.modules.reporting.JUnitXMLReporter

  local:

    class: bzt.modules.provisioning.Local

  locust:

    class: bzt.modules.locustio.LocustIOExecutor

  monitoring:

    class: bzt.modules.monitoring.Monitoring

  passfail:

    class: bzt.modules.passfail.PassFailStatus

  pbench:

    class: bzt.modules.pbench.PBenchExecutor

  selenium:

    class: bzt.modules.selenium.SeleniumExecutor

    selenium-tools:

      junit:

        hamcrest-core: ~/.bzt/selenium-taurus/tools/junit/hamcrest-core.jar

        jar-name: compiled.jar

        path: ~/.bzt/selenium-taurus/tools/junit/junit.jar

        selenium-server: ~/.bzt/selenium-taurus/selenium-server.jar

        working-dir: classes

      nose:

        working-dir: classes

  shellexec:

    class: bzt.modules.shellexec.ShellExecutor

  siege:

    class: bzt.modules.siege.SiegeExecutor

provisioning: local

reporting:

- module: final_stats

  test-duration: true

- module: console

services:

- local:

  - metrics:

    - cpu

    - mem

    - bytes-sent

    - bytes-recv

    - disk-read

    - disk-write

    - disk-space

    - engine-loop

  module: monitoring

settings:

  aggregator: consolidator

  artifacts-dir: '%Y-%m-%d_%H-%M-%S.%f'

  check-interval: 1

  check-updates: true

  default-executor: jmeter

  proxy: {}

version: 1.2.0

[ta...@blazemeter.com]

Please tell me the version of your JMeter plugins that used for this jmx writing.

[abbya...@gmail.com]

Initially written with JMeterPlugins-Extras-1.3.0 but as it was not working I tried an earlier version JMeterPlugins-Extras-1.1.2 which also did not work for me.

[ta...@blazemeter.com]

Similar to there is a problem with JMeter plugins versions, you can check it by opening jmx with plugins 1.3.1, i think this version can't see your threads info.
If I'm right, as workaround you can do following:
1. remove apache-jmeter-2.13 directory
2. change in your config required version of plugins from '1.3.1' to '1.3.0'

or point 'path' parameter to your own jmeter.sh with old (1.3.0) plugins.

[Abby Adegun]

It seems to have been a plugin issue afterall. After re-installing jmeter with freshly downloaded plugins, my Ultimate Thread script executed without any issues.

Thank you very much for your help ^_^!!!

[ta...@blazemeter.com]

We're glad to be of use.

[snehalatha danthuri]

Hello team,

I created a jmx file containing ULTIMATE THREAD GROUP: this has the following fields - Rampup, Steadystate, and rampdown.

As I'm trying to execute via Taurus configuration: I found, In the modified JMX file, it's converting to a different thread group according to the parameters passed for the execution section of the YAML file.

And also I found there is no option to set Rampdown param in execution section.

Please find attached YAML, original JMX, Modified JMX after executing bzt command.

YAML:

execution:
  - concurrency: '1'
    hold-for: 2m
    throughput: '1'  
    ramp-up: 1s
    scenario: jmeter
scenarios:
  jmeter:
    script: Throughput.jmx
    properties:
      PAL: true
      SERVER_NAME:
      SERVER_PORT:
      NODE_PORT:
      SERVER_PROTOCOL:
      ROOT_CONTEXT:
      PRPC_NODE_COUNT: 1
      PAL_FILE: pal.xml
      DELAY_OFFSET: 1000
      DELAY_MAXIMUM: 2000
      RAMPDOWN_TIME: 20
reporting:
  - module: final-stats
    dump-xml: stats.xml
services:
  - module: monitoring
    ~local:
      - interval: 5s
        logging: true

        metrics:
          - cpu
          - mem

ORIGINAL JMX:

MODIFIED JMX:

Could you please help with this?

Thanks,

Sneha

[grey....@gmail.com]

Hello Sneha.
1. to avoid tg conversion please omit all load params (concurrency, hold-for, throughput, ramp-up).

2. We have not ramp-down param, you're right.

3. please create new thread for new question.

---

Taras