[Date Prev][Date Next]
Re: (ITS#3672) Odd behavior of back meta when tortured by concurrency test
> I'd mark this as suspended right now.
I've spotted the problem; when doing anonymous bind to the targets in the
pool prior to attempting operations, in case of error (e.g. server busy)
no response is being returned to the client. This seldom happens in
normal usage, but under torture it may happen (and actually does if
there's too many and, say, logging is too intensive), e.g. when the target
I've temporarily fixed back-meta to return an error condition (e.g.
LDAP_BUSY); I'll improve this by allowing to configure hings like numer of
retries, timeouts and so on a per-target bassis, so one can have different
policies based on the characteristics of the targets (one may be on a low
bandwidth connection, another may be known to be little responsive and
I also need to check if and how this may affect re22.
A patch is about to come.
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497