The poll loop in slapd_daemon() will first look for a new ldap connection from an ldap listener. If it finds one, it will not look for a new ldaps or ldapi connection. If the server is processing thousands of ldap connection requests per second, this could cause ldaps connections to take a long time, timeout, or accumulate in the ldaps port tcp backlog queue.
0001-Ticket-47359-new-ldap-connections-can-block-ldaps-an.patch 0001-Ticket-47359-new-ldap-connections-can-block-ldaps-an.patch
bce5557..24b751c master -> master commit 24b751c Author: Rich Megginson rmeggins@redhat.com Date: Fri May 10 15:11:13 2013 -0600
9b0834c..56f661c master -> master commit 24b751c Author: Rich Megginson rmeggins@redhat.com Date: Fri May 10 15:11:13 2013 -0600
Fix build breakage in previous commit
56f661c..a541936 master -> master commit a541936 Author: Rich Megginson rmeggins@redhat.com Date: Tue May 21 17:30:50 2013 -0600 Fix Description: Fix more build breakage in previous commit
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=966781
ec592bb..8a1fd07 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 8a1fd07 Author: Rich Megginson rmeggins@redhat.com Date: Fri May 10 15:11:13 2013 -0600 d89bc22..e0328ab 389-ds-base-1.3.0 -> 389-ds-base-1.3.0 commit e0328ab Author: Rich Megginson rmeggins@redhat.com Date: Fri May 10 15:11:13 2013 -0600 c7e0b79..5226ed9 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 commit 5226ed9 Author: Rich Megginson rmeggins@redhat.com Date: Fri May 10 15:11:13 2013 -0600
Metadata Update from @rmeggins: - Issue set to the milestone: 1.2.11.22
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/696
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.