You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2016/11/03 16:55:39 UTC

[Bug 60338] New: Dashboard does not show correct number of threads where the test plan is executed over two or more remote servers

https://bz.apache.org/bugzilla/show_bug.cgi?id=60338

            Bug ID: 60338
           Summary: Dashboard does not show correct number of threads
                    where the test plan is executed over two or more
                    remote servers
           Product: JMeter
           Version: 3.0
          Hardware: PC
            Status: NEW
          Severity: major
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: anthony.kearns@ymail.com
  Target Milestone: ---

I have a test plan which is configured for 35 threads. I run the test plan on
two remote servers so the total active threads should be 70. When i look at the
thread group related graphs on the dashboard i only see 35 threads being
reported. I would expect that the dashboard should show 70 threads.

I have attached my results.jtl file and a screenshot of the thread group
related graphs on the dashboard.

Let me know if you need more info....

Maybe this is already addressed by bug 60171 ?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 60338] Dashboard does not show correct number of threads where the test plan is executed over two or more remote servers

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60338

--- Comment #1 from anthony.kearns@ymail.com <an...@ymail.com> ---
Created attachment 34419
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34419&action=edit
results zip file with results.jtl

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 60338] Dashboard does not show correct number of threads where the test plan is executed over two or more remote servers

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60338

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #2 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hi,
This is fixed in nightly build but ensure you read the docs because you need to
add to thread group something that uniquely identifies thread group per
injector.

Feedback is very welcome.
Regards

*** This bug has been marked as a duplicate of bug 60171 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 60338] Dashboard does not show correct number of threads where the test plan is executed over two or more remote servers

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60338

anthony.kearns@ymail.com <an...@ymail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All
                 CC|                            |anthony.kearns@ymail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 60338] Dashboard does not show correct number of threads where the test plan is executed over two or more remote servers

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60338

--- Comment #3 from anthony.kearns@ymail.com <an...@rightside.co> ---
Hi, I don't really understand this comment.....

"add to thread group something that uniquely identifies thread group per
injector."

In my case the test plan has one thread group and the plan is 35 threads. So
when the plan is sent to two remote slaves each slave runs 35 threads and hence
the total threads is 70 started and 70 active. If is send this results.jtl file
to blaze Meter sense site it identifies correctly that there are 70 threads.

Maybe I just need to update the dashboard changes to my jmeter instance to try
out the changes?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 60338] Dashboard does not show correct number of threads where the test plan is executed over two or more remote servers

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60338

--- Comment #4 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
(In reply to anthony.kearns@ymail.com from comment #3)
> Hi, I don't really understand this comment.....
> 
> "add to thread group something that uniquely identifies thread group per
> injector."
> 
> In my case the test plan has one thread group and the plan is 35 threads. So
> when the plan is sent to two remote slaves each slave runs 35 threads and
> hence the total threads is 70 started and 70 active.

Please read the nightly build doc about how to configure it.
so that it works in jmeter.
You need for example to add ${__machineName} in the thread group name


> If is send this
> results.jtl file to blaze Meter sense site it identifies correctly that
> there are 70 threads.


I don't know how blazemeter works, but JMeter has no relation with it.
If you're running your test within blazemeter then report it to their support.
If it's plain jmeter then follow my advice and give feedback.

Thanks



> Maybe I just need to update the dashboard changes to my jmeter instance to
> try out the changes?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 60338] Dashboard does not show correct number of threads where the test plan is executed over two or more remote servers

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60338

anthony.kearns@ymail.com <an...@rightside.co> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |VERIFIED

--- Comment #5 from anthony.kearns@ymail.com <an...@rightside.co> ---
Thank you, i get it now. Will close this bug now as a dupe of the one you
mentioned.

thanks again

-- 
You are receiving this mail because:
You are the assignee for the bug.