<br><br><div class="gmail_quote">On Thu, Sep 8, 2011 at 3:10 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 9/8/11 3:02 PM, "Jim Fox" <<a href="mailto:fox@washington.edu">fox@washington.edu</a>> wrote:<br>
><br>
>We use connection pooling for all our accesses to LDAP. We use TLS, and<br>
>the overhead of starting up a new session on each query seemed excessive<br>
>to me. Our openldap servers keep the sessions open all day.<br>
<br>
</div>Are you using any of the validation options in the pooling element? I see<br>
the retry count defaults to 1 inside the vt-ldap code, so I'm sure no<br>
matter what I do, it's just going to drop the failed connection and retry.<br>
With some cases like that, the problem is if the closed connections hangs<br>
(very common with database pools) but these don't seem to.<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br></div><div>The most common hangs we've seen and heard about are caused by hardware load balancers that don't send resets to both client and server. I haven't tested the read timeout that Ryan mentioned, but typically setting a timeLimit and doing validation will work around that issue.</div>
<div><br></div><div>--Daniel Fisher</div><div><br></div></div>