Bug 1523505

Summary: opened connection are hanging, no longer poll [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact: Marc Muehlfeld <mmuehlfe>
Priority: urgent    
Version: 7.5CC: enewland, gparente, ipa-maint, ipa-qe, ksiddiqu, mreynolds, mreznik, msauton, nkinder, nsoman, pvoborni, rcritten, rmeggins, spoore, ssorce, tbordaz, tmihinto, tscherf
Target Milestone: rcKeywords: Regression, TestBlocker, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.6.1-25.el7_4 Doc Type: Bug Fix
Doc Text:
Previously, when a connection received a high operation rate, Directory Server stopped to poll the connection in certain situations. As a consequence, new requests on the connection were not detected and processed. With this update, Directory Server correctly decides whether a connection has to be polled. As a result, connections with a high request rate no longer remain unprocessed.
Story Points: ---
Clone Of: 1514033 Environment:
Last Closed: 2018-01-25 12:22:50 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:
Bug Depends On: 1514033    
Bug Blocks:    

Description Oneata Mircea Teodor 2017-12-08 07:37:04 UTC
This bug has been copied from bug #1514033 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 3 thierry bordaz 2017-12-08 17:13:37 UTC
The bug fix is pushed upstream -> POST

Comment 6 Viktor Ashirov 2018-01-05 13:18:07 UTC
Build tested:
389-ds-base-1.3.6.1-25.el7_4.x86_64

I was running ipa-server-install/uninstall in a loop for 2 days and I can't hit the error described in the original bz. 

Marking as VERIFIED, SanityOnly.

Comment 10 errata-xmlrpc 2018-01-25 12:22:50 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.

https://access.redhat.com/errata/RHSA-2018:0163