Am 29. Oktober 2017 19:21:19 MEZ schrieb Philippe Mouawad <[email protected]>: >Hello, >Yes please open a bugzilla and provide: >- an excerpt of your test plan >- jmeter.log >- 3 thread dumps at 5s distance when issue occurs
I think the most likely cause is the premature end of an iteration - "go to next loop iteration". We probably need to add an iteration listener that unlocks the locks on iteration start. Regards, Felix > >Thank you > >On Sunday, October 29, 2017, Shmuel Krakower <[email protected]> >wrote: > >> Hello, >> It has been a while since I've participated in the users' list.. >> >> I am running a stress test with multiple thread groups and I'm using >the >> Critical Section Controller to prevent a specific action from taking >place >> multiple times on the same time. >> >> I notice that the results are much lower than the required throughput >I >> plan to achieve. >> After looking into the jmeter logs I notice many of my threads were >> actually "locked" waiting for the critical section and this is the >reason I >> am not reaching my target RPS. >> >> The log show entries such as: >> WARN - jmeter.control.CriticalSectionController: Lock global_lock >not >> released in:Critical Section Controller, releasing in threadFinished >> >> 'global_lock' - is just the default text used in the controller. But >it >> clearly shows that at some point one of the threads keeps the lock >busy >> which in turn just block the others. >> >> Some ideas/questions: >> Maybe it would make sense to have a timeout on the lock? >> Is it possible that an exception raised inside the critical section, >> prevented it from being released? >> The main suspect I have in my test plan is a Test Action element I >use >> which is set to "Go to next loop iteration" in some cases, maybe >that's the >> one which doesn't release the critical section?... >> >> Would it help if I take a thread dump and share it here? >> Should I open a defect in Bugzilla for that? >> Has anyone faced such an issue before? >> >> Best, >> Shmuel Krakower. >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
