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 1044146 - Add a warning message when a connection hits the max number of threads
Summary: Add a warning message when a connection hits the max number of threads
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
low
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 21:24 UTC by Nathan Kinder
Modified: 2020-09-13 20:35 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.3.3.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 09:29:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 719 0 None closed Add a warning message when a connection hits the max number of threads 2021-02-03 19:28:22 UTC
Red Hat Product Errata RHSA-2015:0416 0 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 14:26:33 UTC

Description Nathan Kinder 2013-12-17 21:24:39 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47382

During investigation related to ticket 47366, an issue was tracked down to a connection reaching the max threads per connection limit.  Specifically, this was with the referential integrity plug-in.

Adding a warning message would help in tracking these sorts of issues down.  I'm not sure if this can be done in such a way that the warnings are not too frequent.  There are certain workloads that might trigger the limit to be hit often, which would not necessarily be a bad thing.  We don't want to pollute the logs with warnings that are not important.  We should investigate this and see if it makes sense to add a warning.
Comment 5 Amita Sharma 2014-12-18 14:19:15 UTC 
[root@dhcp201-126 yum.repos.d]# rpm -qa | grep 389
389-ds-base-1.3.3.1-10.el7.x86_64
389-ds-base-libs-1.3.3.1-10.el7.x86_64


[root@dhcp201-126 yum.repos.d]# ldapsearch -D "cn=directory manager" -w Secret123 -xLLL -b "cn=monitor" -s base objectclass=* connection
dn: cn=monitor
connection: 64:20141218141242Z:2:1:-:cn=directory manager:0:0:0


[root@dhcp201-126 yum.repos.d]# ldapmodify -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=delete-me,dc=example,dc=com
> changetype: add
> objectClass: top
> objectClass: groupofuniquenames
> cn: delete-me
> EOF
adding new entry "cn=delete-me,dc=example,dc=com"

[root@dhcp201-126 yum.repos.d]# ldapmodify -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=referential integrity postoperation,cn=plugins,cn=config
> changetype: modify
> replace: nsslapd-pluginEnabled
> nsslapd-pluginEnabled: on
> EOF
modifying entry "cn=referential integrity postoperation,cn=plugins,cn=config"

[root@dhcp201-126 yum.repos.d]# ldapmodify -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=config
> changetype: modify
> replace: nsslapd-maxthreadsperconn
> nsslapd-maxthreadsperconn: 1
> EOF
modifying entry "cn=config"

[root@dhcp201-126 yum.repos.d]# ldapmodify -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=delete-me,dc=example,dc=com
> changetype: delete
> EOF
deleting entry "cn=delete-me,dc=example,dc=com"


[root@dhcp201-126 yum.repos.d]# ldapsearch -D "cn=directory manager" -w Secret123 -xLLL -b "cn=monitor" -s base objectclass=* connection
dn: cn=monitor
connection: 64:20141218141650Z:2:1:-:cn=directory manager:0:8:10

[root@dhcp201-126 yum.repos.d]# ldapsearch -D "cn=directory manager" -w Secret123 -xLLL -b "cn=monitor" -s base objectclass=* connection
dn: cn=monitor
connection: 64:20141218141702Z:2:1:-:cn=directory manager:0:11:13

[root@dhcp201-126 yum.repos.d]# ldapsearch -D "cn=directory manager" -w Secret123 -xLLL -b "cn=monitor" -s base objectclass=* connection
dn: cn=monitor
connection: 64:20141218141709Z:2:1:-:cn=directory manager:0:14:16

Hence VERIFIED.
Comment 7 errata-xmlrpc 2015-03-05 09:29:47 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/RHSA-2015-0416.html
Note You need to log in before you can comment on or make changes to this bug.