GitLab

During response processing, an upstream connection could be marked ready
after a different bind had already been allocated to it, thus allowing
two binds to be in progress on the same connection.

Ondřej Kuzník authored Dec 13, 2017 and Ondřej Kuzník committed Nov 17, 2020

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.

Ondřej Kuzník authored Nov 22, 2017 and Ondřej Kuzník committed Nov 17, 2020

In preparation for operation timeout events.

Ondřej Kuzník authored Jun 30, 2017 and Ondřej Kuzník committed Nov 17, 2020

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.

Ondřej Kuzník authored Jun 27, 2017 and Ondřej Kuzník committed Nov 17, 2020

Stats now logs all operations, stats2 additionally intermediate messages
(search entries).

Ondřej Kuzník authored May 18, 2017 and Ondřej Kuzník committed Nov 17, 2020

We reset the connection pointer on a destruction attempt, avoid the
spurious asserts.