jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62684] New: Distributed Testing : Add automatically to thread name a prefix to identify engine
Date Wed, 05 Sep 2018 20:09:04 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62684

            Bug ID: 62684
           Summary: Distributed Testing : Add automatically to thread name
                    a prefix to identify engine
           Product: JMeter
           Version: 5.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: p.mouawad@ubik-ingenierie.com
  Target Milestone: ---

Currently when doing distributed testing, by default as there is no default
prefix for threads, the Active Threads Over Time graph will not be correct
unless user adds a prefix as described here:
-
https://jmeter.apache.org/usermanual/generating-dashboard.html#configuration_requirements
------------------------------------------------------------
When using JMeter distributed mode with multiple jmeter-server instances,
ensure you add in your Thread Groups something that uniquely identifies
ThreadGroup for every JVM, example:

ThreadXXX_${__P(JVM_ID)}

where you pass a different JVM_ID property for each jmeter-server through:

-JJVM_ID=i

where i varies between 1 and the number of jmeter-server you are using. 
------------------------------------------------------------
or here:
- https://jmeter-plugins.org/wiki/ActiveThreadsOverTime/

This enhancement will make JMeter automatically add a prefix to thread that
uniquely identifies each server engine.

This is contributed by UbikLoadPack .

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message