Bug 1290243
Summary: | SimplePagedResults -- in the search error case, simple paged results slot was not released. | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Noriko Hosoi <nhosoi> | |
Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> | |
Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> | |
Severity: | urgent | Docs Contact: | Petr Bokoc <pbokoc> | |
Priority: | urgent | |||
Version: | 6.0 | CC: | amsharma, jgalipea, msauton, nkinder, pbokoc, rmeggins | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | 389-ds-base-1.2.11.15-71.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Simple paged results slots are now being correctly released after search failure
Previously, if a simple paged results search failed in the Directory Server backend, its slot was not released, which caused the connection object to accumulate unreleased slots over time. This problem has been fixed, and slots are now correctly released in the event of a search failure.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1290722 (view as bug list) | Environment: | ||
Last Closed: | 2016-05-10 19:22:25 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: | ||||
Bug Blocks: | 1290722 |
Description
Noriko Hosoi
2015-12-09 22:32:18 UTC
This is fixed. [31/Dec/2015:05:46:59 -0500] conn=1 op=3036 RESULT err=0 tag=101 nentries=0 etime=0 notes=P pr_idx=0 in access long after a long time execution. [root@mgmt3 export]# rpm -qa | grep 389 389-ds-base-libs-1.2.11.15-71.el6.x86_64 389-ds-base-1.2.11.15-71.el6.x86_64 389-ds-base-debuginfo-1.2.11.15-71.el6.x86_64 389-ds-base-devel-1.2.11.15-71.el6.x86_64 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://rhn.redhat.com/errata/RHBA-2016-0737.html |