[prev in list] [next in list] [prev in thread] [next in thread] 

List:       turbine-jcs-dev
Subject:    DO NOT REPLY [Bug 51733] New: SyncTimer is messed up if you a
From:       bugzilla () apache ! org
Date:       2011-08-29 5:41:55
Message-ID: bug-51733-55412 () https ! issues ! apache ! org/bugzilla/
[Download RAW message or body]

https://issues.apache.org/bugzilla/show_bug.cgi?id=51733

             Bug #: 51733
           Summary: SyncTimer is messed up if you a interrupt a test plan
           Product: JMeter
           Version: 2.5
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
        AssignedTo: notifications@jakarta.apache.org
        ReportedBy: gruwez@gmail.com
    Classification: Unclassified


Scenario:
Use a SyncTimer in your test plan and set it to block up to a number of
threads, e.g. 5
Run the test and interrupt it before all 5 threads have been blocked. Assume 3
threads have been blocked so far.
Rerun the test and let it run.
You will notice the SyncTimer will unblock after 2 threads and not 5.

The reason is that when the test is started, the clone() method is called on
the SyncTimer to created a new one. Since the test interruption left the
previous SyncTimer with already 3 threads "registered", this value (3) will be
used in the cloned SyncTimer.

Encountered in JMeter 2.5 r1158837

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]