On Tue, Sep 27, 2011 at 2:16 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">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>On 9/27/11 1:34 PM, "Tom Poage" <<a href="mailto:tfpoage@ucdavis.edu" target="_blank">tfpoage@ucdavis.edu</a>> wrote:<br>
><br>
>This suggests the connection pool might be empty:<br>
<br>
</div>The empty strategy is what gets used when there is no pool. Every checkout<br>
of the pool creates a connection and the checkin destroys it.<br>
<br>
A recent poster indicated that leaving out a pool config causes the data<br>
connector to still reuse some connections. If that's true, it's below the<br>
layers of software and somewhere inside the JVM, because the code in the<br>
IdP is pretty clearly not doing any reuse.<br><font color="#888888"><br></font></blockquote><div><br></div><div>I'd be curious to know if that's happening. The JNDI LdapContext *may* spawn new connections under heavy load, but this sounds like the opposite behavior.</div>
<div><br></div><div>--Daniel Fisher</div><div><br></div>
</div>