Bug #4464
closed
Connection releasing of test LDAP server is incorrect, leading to lost of connection
Added by François ARMAND about 11 years ago.
Updated about 10 years ago.
Category:
Architecture - Code maintenance
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).
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.
- 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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset scala-ldap:commit:1bb6537cf954bb6fbc1d338c237762eb119264f6.
Applied in changeset scala-ldap:commit:e3ddde8873fe4b4c32d4ef49f11f555c52ecbea5.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
- Category changed from 40 to Architecture - Code maintenance
Also available in: Atom
PDF