Handling empty LDAP connection pools on IdP start-up

[Wessel, Keith]

All,

We recently added connection pooling to our LDAP data connectors to speed thing sup. I was hoping, based on past experience with database connection pooling, to allow the IdP to go about its business if it started up and couldn't create any connections in the pool. That is, if the LDAP server was unavailable, it would go ahead and start and keep trying to create LDAP connections. This shouldn't happen since our LDAP server is clustered, but I'm all for making things as fault-proof as possible.

Yesterday morning, our test LDAP cluster was down when our test IdP nodes restarted, and they all reported not being able to initialize the LDAP connection pool.

I have this in my LDAP data connectors:
	<ConnectionPool maxPoolSize="20" blockWaitTime="PT5S"
	    expirationTime="PT10M" failFastInitialize="false" 
	    validatePeriodically="true" validateTimerPeriod="PT10M"
	    validateDN="%{idp.attribute.resolver.LDAP.bindDN" />

I left out the min pool size with the impression that it defaults to 0. I also didn't' see any params discussing an initial pool size, assuming that it was the ame as the min pool size.

Am I overlooking something? How do I get the pool to initialize even if it can't create connections?

Thanks,
Keith