2. What is the nature and description of the request?
Implement SO_KEEPALIVE in network calls
3. Why does the customer need this? (List the business requirements here)
Customer's RHDS being affected by lingering TCP connections that are not
correctly closed (refer to https://access.redhat.com/kb/docs/DOC-44459).
From RFC 1122:
A TCP keep-alive mechanism should only be invoked in
server applications that might otherwise hang
indefinitely and consume resources unnecessarily if a
client crashes or aborts a connection during a network
With this implementation, RHDS would be more resilient to
misconfigured/problematic clients, at a minimum cost.
4. How would the customer like to achieve this? (List the functional
Implement SO_KEEPALIVE in network calls.
5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
# netstat -tnpo
tcp 0 0 10.66.129.184:40223 10.64.10.12:636
ESTABLISHED 1337/ns-slapd keepalive (2740.13/0/0)
6. Is there already an existing RFE upstream or in Red Hat bugzilla?
7. How quickly does this need resolved? (desired target release)
8. Does this request meet the RHEL Inclusion criteria (please review)
9. List the affected packages
10. Would the customer be able to assist in testing this functionality if
batch update moving tickets to future
[mareynol@localhost ds]$ git merge ticket191
ldap/servers/slapd/daemon.c | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
[mareynol@localhost ds]$ git push
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 830 bytes, done.
Total 6 (delta 4), reused 0 (delta 0)
0594d5f..2335995 master -> master
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=834061
Added initial screened field value.
Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.2.11.a1
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:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
to comment on this ticket.