https://issues.apache.org/bugzilla/show_bug.cgi?id=56728
Bug ID: 56728
Summary: Implement Critical Section Controller
Product: JMeter
Version: Nightly (Please specify date)
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Created attachment 31816
--> https://issues.apache.org/bugzilla/attachment.cgi?id=31816&action=edit
implementation of critical section controller
Hi folks!
In my work i have tests with many users and threads, but sometimes i have
requests, which shouldn't execute simultaneously on one user.
For example, users changes settings in his profile, but only one user can
change his information simultaneously. In default JMeter doesn't support this
behavior.
Critical Section Controller is a simple controller, which create lock with name
(let us say his login/username) and other threads will block, if they try to go
into the critical section with same name.
For improvement of this concept we can add policies, such as "blocking lock",
and "try lock" for powerful scenarios.
I tried to use many bicycles with BeanShell, but all BeanShell scripts runs
under lock on Interpreter and with named locks i have many deadlocks problems:)
Bicycles with jsr223 better, but they are to complex.
This concept is easy and clearly.
--
You are receiving this mail because:
You are the assignee for the bug.
