Hi Lothar, can you describe when the error occurs? * On connect/bind * When exanding the DIT * When executing some complex search query? * For modify operations are only for searches or both?
Does the error happen immediately or after some timeout (like 10 or 30 seconds)? If you have a stacktrace (in error dialog or in log file) could you please post it? There is a configurable "Connection timeout" in the connection properties, but I guess you already tried to change that? I'll try to reproduce by connection to an ApacheDS where I put some sleeps into the code... Kind Regards, Stefan On 6/9/20 3:48 PM, Lothar Haeger wrote: > Sorry for the redundancy, the other error I see a lot is > ERR_04170_TIMEOUT_OCCURED > >> Am 09.06.2020 um 15:46 schrieb Lothar Haeger <[email protected]>: >> >> So I've updated to M15, which dumps JNDI and enforces the Apache LDAP API. >> Right from the start I got lots of ERR_04169_RESPONSE_QUEUE_EMPTIED and >> ERR_04169_RESPONSE_QUEUE_EMPTIED when working with highly loaded eDirectory >> servers, to an extend that I dumped M15 and went back to M14 again. >> >> M14 shows the same problems when a connection is using the Apache API but >> works just fine with JNDI. Seems like the timeout used in the Apache API is >> not configurable through the Apache DS interface, or I just did not find it. >> >> Any hints on how to make M15 with Apache API work as reliably as M14 does >> with JNDI? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
