Bug 1290243 - SimplePagedResults -- in the search error case, simple paged results slot was not released.
SimplePagedResults -- in the search error case, simple paged results slot was...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Noriko Hosoi
Viktor Ashirov
Petr Bokoc
: ZStream
Depends On:
Blocks: 1290722
  Show dependency treegraph
Reported: 2015-12-09 17:32 EST by Noriko Hosoi
Modified: 2016-05-10 15:22 EDT (History)
6 users (show)

See Also:
Fixed In Version: 389-ds-base-
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)
Last Closed: 2016-05-10 15:22:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Noriko Hosoi 2015-12-09 17:32:18 EST
1. Install and configure the Directory Server WITHOUT a suffix "o=redhat".
2. Compile paged_def.c after adjusting the Directory Manager's password.
   Note: the suffix o=redhat should not be adjusted.
3. Run the compiled paged_def.
4. The access log would contain the result line with "err=32" AND a large pr_idx. E.g.,
> [..] conn=1 op=130870 RESULT err=32 tag=101 nentries=0 etime=0 notes=P pr_idx=43623
Comment 4 Amita Sharma 2015-12-31 05:48:08 EST
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
Comment 6 errata-xmlrpc 2016-05-10 15:22:25 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.