Bug 957305

Summary: DS instance crashes under a high load
Product: Red Hat Enterprise Linux 6 Reporter: Rich Megginson <rmeggins>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Sankar Ramalingam <sramling>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: greve, jgalipea, lnovich, nhosoi, nkinder, vanmeeuwen+fedora
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Under a very high load (hundreds of simultaneous connections and operations) the directory server could encounter a race condition in the connection handling code. Consequence: The directory server would crash. Fix: Move the code that updates the connection objects inside the connection mutex. Result: Directory server does not crash under high loads.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 21:07:16 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-04-27 01:57:35 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47349

Under heavy connection load, crashes are being randomly encountered.  This happens because we allocate and set c_private in the connection object after we put the connection on the active list.  Another thread can try to dereference c_private before it is allocated.

Comment 6 Sankar Ramalingam 2013-09-18 11:31:47 UTC
Marking the bugzilla as Verified since no regression found with the latest build - 389-ds-base-1.2.11.15.23.

Comment 7 errata-xmlrpc 2013-11-21 21:07:16 UTC
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