<br><br><div class="gmail_quote">On Thu, Sep 8, 2011 at 4:08 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;">
Thanks...<br>
<div class="im"><br>
On 9/8/11 3:52 PM, "Daniel Fisher" <<a href="mailto:dfisher@vt.edu">dfisher@vt.edu</a>> wrote:<br>
><br>
>- are there ways to maintain connections and avoid the timeouts from the<br>
>client end?<br>
><br>
>You should be able to configure periodic validation to guarantee your<br>
>connections are always alive.<br>
<br>
</div>With AD, I'm seeing the connections close on the order of minutes, if not<br>
sooner. That doesn't seem to fit with that strategy, so perhaps AD is<br>
different.<br>
<br>
I'll probably have to just try it under load and see how they behave. Even<br>
if they close fast, constant use would keep them open.<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br></div><div>That's sounds very aggressive, and would certainly discourage pooling. Perhaps they don't want you holding connections open? We configure keep-alive on the servers (OpenLDAP, not AD) to encourage it.</div>
<div><br></div><div>--Daniel Fisher</div><div><br></div></div>