https://bz.apache.org/bugzilla/show_bug.cgi?id=62806
Bug ID: 62806
Summary: ModuleController behaves differently wether in GUI or
Non GUI mode
Product: JMeter
Version: 2.13
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.1
Created attachment 36191
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36191&action=edit
Test plan screenshot
Hello,
Working with 3rd party plugin we noticed a difference in behaviour between GUI
and NON GUI mode.
One particular 3rd party component that implemented NoThreadClone was behaving
in a wrong way in NON GUI Mode.
See:
- https://groups.google.com/forum/#!topic/jmeter-plugins/YEU-nstQ4oc
After further analysis it appears issue is in Core JMeter .
When running a test in GUI mode , a clone tree withour honouring NoThreadClone
happens:
-
https://github.com/apache/jmeter/blob/v5_0/src/core/org/apache/jmeter/gui/action/Start.java#L205
But in GUI mode, so such thing happens.
This triggers an issue when you use at least twice a ModuleController that
references a Component that implements NoThreadClone.
In the attached test plan, we have:
- TG-Participant1-Input using a ModuleController-Sender referencing
Simple-Controller-Referenced
- TG-Participant2-Input using a ModuleController-Sender referencing
Simple-Controller-Referenced
We end up having in NON GUI only 1 instance of NoThreadClone-Element while in
GUI mode we have 2.
--
You are receiving this mail because:
You are the assignee for the bug.
