Bug 968503
Summary: | flush_ber error sending back start_tls response will deadlock | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Rich Megginson <rmeggins> |
Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | jgalipea, jrusnack, lnovich, nhosoi, nkinder, rmeggins |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 389-ds-base-1.2.11.15-22.el6 | Doc Type: | Bug Fix |
Doc Text: |
Cause: The server is processing a startTLS request and gets an error (network error usually) attempting to write the response back to the client.
Consequence: The server will hang and become unresponsive to this an any new connection request, due to a deadlock in the connection handling code.
Fix: Make sure the connection is not locked when this error condition occurs.
Result: Server correctly processes startTLS requests when there are network errors, and continues to work fine for established and new connection requests.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-21 21:08:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rich Megginson
2013-05-29 19:35:51 UTC
Is it possible to automate this ? If yes, could you please add verification steps ? (In reply to Ján Rusnačko from comment #6) > Is it possible to automate this ? If yes, could you please add verification > steps ? We do not know how to reproduce this, much less automate. The customer has verified that the patch works, so I think we will just have to mark the bug as verified by customer. Verified sanity only on 389-ds-base-1.2.11.15-24.el6. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1653.html |