On Thu, Sep 8, 2011 at 4:24 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>></span> wrote:<br><div class="gmail_quote"><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 4:14 PM, "Daniel Fisher" <<a href="mailto:dfisher@vt.edu">dfisher@vt.edu</a>> wrote:<br>
><br>
>That's sounds very aggressive, and would certainly discourage pooling.<br>
>Perhaps they don't want you holding connections open? We configure<br>
>keep-alive on the servers (OpenLDAP, not AD) to encourage it.<br>
<br>
</div>There's also a load balancer involved (per your other comment) that could<br>
be affecting it.<br>
<br>
One thing that didn't make sense to me was that the expirationTime setting<br>
in the connector is documented as causing the pool to eject stale<br>
connections once they're unused for that length of time. If that's shorter<br>
than the validation interval, I wouldn't expect the background validator<br>
to even try those connections and see that they're closed, since they<br>
should have just expired by then.<br><font class="Apple-style-span" color="#888888"><br></font></blockquote><div><br></div><div>I think that's correct, if I understand what you're saying. A lower expirationTime will cause those connections to be removed before the validator even runs. So the connections won't be in the pool and therefore won't be validated.</div>
<div><br></div><div>--Daniel Fisher</div><div> </div></div>