Bug 61663 - Add Dead lock detection
Summary: Add Dead lock detection
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 3.3
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-25 08:12 UTC by orimarko
Modified: 2017-10-26 05:12 UTC (History)
1 user (show)



Attachments
Add warning for Critical Section Controller (694 bytes, patch)
2017-10-25 09:06 UTC, orimarko
Details | Diff
Update patch of xdocs (642 bytes, patch)
2017-10-26 05:12 UTC, orimarko
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description orimarko 2017-10-25 08:12:58 UTC
You can create a dead lock using Critical Section Controller and make JMeter stuck If inside lock A add lock B and inside other lock B add lock A with a few threads there's a dead lock.

Need to add Dead locks detection before test start
Comment 1 orimarko 2017-10-25 09:06:03 UTC
Created attachment 35460 [details]
Add warning for Critical Section Controller

Add warning for Critical Section Controller reference
Comment 2 Philippe Mouawad 2017-10-25 18:45:24 UTC
Thanks for your contribution.
Few notes:

- JMeter documentation is managed in xdocs and HTML is generated from it. So your patch should concern this part.

- Deadlock will occur if the locks are taken in different order, maybe your note should highlight this.

Thanks
Comment 3 orimarko 2017-10-26 05:12:38 UTC
Created attachment 35462 [details]
Update patch of xdocs

Update patch of xdocs component_reference.xml
Add comment on "if the locks are taken in different order"