Diagnosing LDAP connection errors.
dfisher at vt.edu
Tue Sep 27 22:10:45 BST 2011
On Tue, Sep 27, 2011 at 2:16 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 9/27/11 1:34 PM, "Tom Poage" <tfpoage at ucdavis.edu> wrote:
> >This suggests the connection pool might be empty:
> The empty strategy is what gets used when there is no pool. Every checkout
> of the pool creates a connection and the checkin destroys it.
> A recent poster indicated that leaving out a pool config causes the data
> connector to still reuse some connections. If that's true, it's below the
> layers of software and somewhere inside the JVM, because the code in the
> IdP is pretty clearly not doing any reuse.
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users