| Summary: | SyncTimer counter is not reset when scenario is stopped | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | roger.bolsius |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 2.1.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Attachments: | Test case | ||
Created attachment 17081 [details]
Test case
Thanks for the report and test case. Fix has been committed to 2.1 branch. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1641 |
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.