Trying to clarify the situation of that long pending connection issue.
The fix for https://pagure.io/389-ds-base/issue/48184 introduced a regression and was backout https://pagure.io/389-ds-base/issue/49569#comment-502760
This new ticket is to enhance the original fix of 48184 so that it does not create 49569
The bug we want to fix here is: At shutdown, close the remaining established connections that are still managed by nunc-stans.
The bug exists in all nunc-stans versions so 1.3.6 and after
Difficult to say, I would expect this bug to be hit systematically for any pending connections (like the ones with lib389 tests).
Note sure what is the symptom of that bug.
Note sure. May be something like
connection_release_nolock_ext - conn=0 fd=0 Attempt to release connection that is not acquired
no message
Open by mistake. I will continue to use https://pagure.io/389-ds-base/issue/48184
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2756
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: duplicate)
Login to comment on this ticket.