Bug 62684 - Distributed Testing : Add automatically to thread name a prefix to identify engine
Summary: Distributed Testing : Add automatically to thread name a prefix to identify e...
Status: RESOLVED FIXED
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.0
Hardware: All All
: P2 enhancement (vote)
Target Milestone: JMETER_5.0
Assignee: JMeter issues mailing list
URL:
Keywords: FixedInTrunk
Depends on:
Blocks:
 
Reported: 2018-09-05 20:09 UTC by Philippe Mouawad
Modified: 2018-09-05 21:00 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2018-09-05 20:09:04 UTC
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 .
Comment 1 Philippe Mouawad 2018-09-05 21:00:19 UTC
pmouawad@apache.org
10:17 PM (42 minutes ago)
 to commits

Author: pmouawad
Date: Wed Sep  5 20:17:14 2018
New Revision: 1840157

URL: http://svn.apache.org/viewvc?rev=1840157&view=rev
Log:
Bug 62684 - Distributed Testing : Add automatically to thread name a prefix to identify engine
Bugzilla Id: 62684

Modified:
    jmeter/trunk/src/core/org/apache/jmeter/engine/RemoteJMeterEngineImpl.java
    jmeter/trunk/src/core/org/apache/jmeter/threads/ThreadGroup.java
    jmeter/trunk/src/core/org/apache/jmeter/util/JMeterUtils.java
    jmeter/trunk/xdocs/changes.xml
    jmeter/trunk/xdocs/usermanual/generating-dashboard.xml



pmouawad@apache.org
10:49 PM (10 minutes ago)
 to commits

Author: pmouawad
Date: Wed Sep  5 20:49:47 2018
New Revision: 1840160

URL: http://svn.apache.org/viewvc?rev=1840160&view=rev
Log:
Bug 62684 - Distributed Testing : Add automatically to thread name a prefix to identify engine
Fix test failure
Bugzilla Id: 62684

Modified:
    jmeter/trunk/bin/testfiles/BatchTestLocalRemote.csv
    jmeter/trunk/bin/testfiles/BatchTestLocalRemote.jmx
    jmeter/trunk/bin/testfiles/BatchTestLocalRemote.xml



Author: pmouawad
Date: Wed Sep  5 20:59:08 2018
New Revision: 1840161

URL: http://svn.apache.org/viewvc?rev=1840161&view=rev
Log:
Bug 62684 - Distributed Testing : Add automatically to thread name a prefix to identify engine
Fix test failure
Bugzilla Id: 62684

Modified:
    jmeter/trunk/bin/testfiles/BatchTestLocal.csv
    jmeter/trunk/bin/testfiles/BatchTestLocal.jmx
    jmeter/trunk/bin/testfiles/BatchTestLocal.xml