RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1278729 - Share nsslapd-threadnumber in the case nunc-stans is enabled, as well.
Summary: Share nsslapd-threadnumber in the case nunc-stans is enabled, as well.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1278584
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 10:02 UTC by Jan Kurik
Modified: 2015-12-08 10:33 UTC (History)
6 users (show)

Fixed In Version: 389-ds-base-1.3.4.0-20.el7_2
Doc Type: Bug Fix
Doc Text:
Previously, when nunc-stans was enabled, the default thread number was 3, and the thread number was controlled by the MAX_THREADS environment variable. With this update, the value of the nsslapd-threadnumber configuration parameter is used instead of obtaining the thread number from MAX_THREADS.
Clone Of: 1278584
Environment:
Last Closed: 2015-12-08 10:33:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2572 0 normal SHIPPED_LIVE 389-ds-base bug fix update 2015-12-08 15:33:39 UTC

Description Jan Kurik 2015-11-06 10:02:05 UTC
This bug has been copied from bug #1278584 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 4 Viktor Ashirov 2015-11-26 22:43:42 UTC
Build tested:
389-ds-base-1.3.4.0-21.el7_2.x86_64

# tail -n1 /etc/profile
export MAX_THREADS=100

nsslapd-threadnumber: 30
nsslapd-enable-nunc-stans: off

# ps huH p $(pidof ns-slapd) | wc -l
41

nsslapd-enable-nunc-stans: on
# ps huH p $(pidof ns-slapd) | wc -l
72


On the older version (389-ds-base-1.3.4.0-19.el7.x86_64):

nsslapd-enable-nunc-stans: off
# ps huH p $(pidof ns-slapd) | wc -l
41

nsslapd-enable-nunc-stans: on
# ps huH p $(pidof ns-slapd) | wc -l
142

Looks like nunc-stans created additional thread pool (30 + 100 + 12 service threads). And on a new version it's 30 + 30 + 12. So the original issue is fixed, so I mark this bug as VERIFIED. For the mentioned issue new bug will be opened.

Comment 6 errata-xmlrpc 2015-12-08 10:33:54 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://rhn.redhat.com/errata/RHBA-2015-2572.html


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