- 17 Nov, 2020 40 commits
-
-
Introduces pinned operations. When SASL bind finishes, we might still have to maintain a link between the client an an upstream for future bind operations if we got a SASL Bind in Progress result code. We zero out the msgids and remember a server-unique identifer on the client and the relevant operation that lets us retrieve that link again. This operation is reclaimed just like anything else when connections drop. Hopefully, this should work for LDAP TXN and VC Exop support with SASL later as well since it allows for many-to-many links to exist.
-
-
-
-
-
In preparation for operation timeout events.
-
-
-
-
-
-
-
-
-
-
-
-
-
When the pdu processing limit is hit, we still attempt to read another PDU. If we succeed, the ber_get_next call in the read callback will abort since a full PDU is already present.
-
-
Stats now logs all operations, stats2 additionally intermediate messages (search entries).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
We reset the connection pointer on a destruction attempt, avoid the spurious asserts.
-
Do not log when receiving the last bytes on a connection. Log failed writes.
-
-
This alone doesn't make the server do a round robin.
-
There was still a race where the connection could be freed as the operation was still being used.
-
-
