Actions
Bug #4464
closed
Connection releasing of test LDAP server is incorrect, leading to lost of connection
Status:
Released
Priority:
3
Assignee:
Category:
Architecture - Code maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
We use an in memory LDAP server for testing purpose.
The logic implemented to release connection to that server is not correct, actually closing the connection, and so could lead to spurious error when a connection is used to do several request (typically: do a search, and on each result, do a delete).
Updated by François ARMAND about 10 years ago
Also, the way we try to know what are the capabilities of the server can lead to an exception where a "I'm not capable" is ok.
Updated by François ARMAND about 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/scala-ldap/pull/9
Updated by François ARMAND about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset scala-ldap:commit:1bb6537cf954bb6fbc1d338c237762eb119264f6.
Updated by Nicolas CHARLES about 10 years ago
Applied in changeset scala-ldap:commit:e3ddde8873fe4b4c32d4ef49f11f555c52ecbea5.
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000077.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE about 9 years ago
- Category changed from 40 to Architecture - Code maintenance
Actions