Bug 37705 - SyncTimer counter is not reset when scenario is stopped
Summary: SyncTimer counter is not reset when scenario is stopped
Status: RESOLVED FIXED
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.1.1
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-30 03:06 UTC by roger.bolsius
Modified: 2005-11-30 17:53 UTC (History)
0 users



Attachments
Test case (12.92 KB, text/plain)
2005-11-30 03:07 UTC, roger.bolsius
Details

Note You need to log in before you can comment on or make changes to this bug.
Description roger.bolsius 2005-11-30 03:06:12 UTC
If the attached test plan is stopped while some threads are waiting in the
synchronizing timer, then the next time the test plan is run it does not wait
for all of the threads to reach the sync timer.

1. Start the test plan (Run->Start)
Sample #  URL
--------- ---------
        1 Connect
        2 Connect
        3 Connect
        4 Connect
        5 Connect
        6 Connect
        7 Connect

2. Once the test reaches say the 7th sample stop the test plan (Run->Stop.)
   Stopping the test should restart the counter in the sync timer, but it
   doesn't.

3. Clear the results (Run->Clear All)
4. Start the test plan again (Run->Start)

Sample #  URL
--------- ---------
        1 Connect
        2 Connect
        3 Connect
        4 Thread3
        5 Thread1
        6 Thread2
        7 Connect
        8 Connect
        ...

Threads #1 through #3 do not wait for the rest of the threads before exiting the
 sync timer.
Comment 1 roger.bolsius 2005-11-30 03:07:04 UTC
Created attachment 17081 [details]
Test case
Comment 2 Sebb 2005-12-01 02:53:35 UTC
Thanks for the report and test case.

Fix has been committed to 2.1 branch.