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 1597530 - Async operations can hang when the server is running nunc-stans [rhel-7.5.z]
Summary: Async operations can hang when the server is running nunc-stans [rhel-7.5.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
Marc Muehlfeld
URL:
Whiteboard:
Depends On: 1597384
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-03 07:22 UTC by Oneata Mircea Teodor
Modified: 2022-03-13 15:11 UTC (History)
7 users (show)

Fixed In Version: 389-ds-base-1.3.7.5-25.el7_5
Doc Type: Bug Fix
Doc Text:
The nunc-stans framework used by Directory Server can register only one handler at a time to read the connection. The next attempt to register a handler waits for the first one to complete. Previously, if the first handler has never been scheduled, for example, because of network inactivity, other threads attempting to register their handlers hung. Certain asynchronous operations sometimes hung if several threads wanted to register a handler on the same connection. With this update, Directory Server considers the state of connections. If already a handler is registered, the framework now decides if it should cancel a not dispatched handler or if it force or ignore the new handler. As a result, asynchronous operations in Directory Server no longer hang.
Clone Of: 1597384
Environment:
Last Closed: 2018-08-16 14:20:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3553761 0 None None None 2018-08-07 09:55:06 UTC
Red Hat Product Errata RHBA-2018:2454 0 None None None 2018-08-16 14:20:12 UTC

Description Oneata Mircea Teodor 2018-07-03 07:22:47 UTC
This bug has been copied from bug #1597384 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 6 Viktor Ashirov 2018-08-05 23:55:47 UTC
Build tested: 389-ds-base-1.3.7.5-25.el7_5.x86_64

Cmocka unit tests pass:

PASS: test_nuncstans
PASS: test_nuncstans_stress_small
PASS: test_nuncstans_stress_large

No hang was observed during the acceptance testing, marking as VERIFIED, SanityOnly.

Comment 8 errata-xmlrpc 2018-08-16 14:20:08 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/RHBA-2018:2454


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