If the timing is just right when a paged result has returned its last result set that a lock(PR_MONITOR) is correctly unlocked/existed. Then when a new connection comes in it deadlocks.
attachment 0001-Ticket-48930-Paged-result-search-can-hang-the-server.patch
b9ab76a..bff1dd4 master -> master commit bff1dd4 Author: Mark Reynolds mreynolds@redhat.com Date: Tue Jul 19 18:28:06 2016 -0400
7738a00..c8e7fc5 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit c8e7fc5
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.4.11
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1989
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.