jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62637] New: Synchronizing Timer set by threads is stuck when adding duration
Date Sun, 19 Aug 2018 12:48:23 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62637

            Bug ID: 62637
           Summary: Synchronizing Timer set by threads is stuck when
                    adding duration
           Product: JMeter
           Version: 4.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: orimarko@gmail.com
  Target Milestone: ---

Created attachment 36099
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36099&action=edit
jmx reproducer

When I'm using Synchronizing Timer set by threads (Number of Simultaneous Users
to Group by) it works well except when using with Thread group's duration,

When it's used together the test hang, probably because of Synchronizing issue,
as documented:

If timeout in milliseconds is set to 0 and number of threads never reaches
"Number of Simultaneous Users to Group by" then Test will pause infinitely.
Only a forced stop will stop it. Setting Timeout in milliseconds is an option
to consider in this case.

Also Runtime Controller isn't a valid replacement for limiting the duration,

Is there other way to limit test duration, but still use some kind of
Synchronization of threads?

Can I add a hook using JSR233 Sampler when test duration over and stop all
threads?

I'm thinking of using Precise Throughput Timer, but it seems over complicated
for this specific requirement.

I can make test no hang if I put a value in Timeout in milliseconds with value
higher than expected in a normal flow, as 10 seconds, 10000, and then after 10
seconds the test stops, but I'm not sure it fixes the issue completely.

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