[JIRA] Created: (SC-170) Expose LDAP pool blockWaitTime on VT pool strategy via connector config
Scott Cantor (JIRA)
noreply at shibboleth.net
Mon Feb 6 15:29:37 GMT 2012
Expose LDAP pool blockWaitTime on VT pool strategy via connector config
-----------------------------------------------------------------------
Key: SC-170
URL: https://issues.shibboleth.net/jira/browse/SC-170
Project: Shibboleth Common - Java
Issue Type: Improvement
Components: Attribute Authority
Affects Versions: 1.3.4
Reporter: Scott Cantor
Assignee: Chad La Joie
If you have a pool configured in the LDAP connector, and the LDAP server doesn't respond or there's a trust-related error preventing connections, the IdP fails to start up but also hangs inside the pool init method waiting for at least one connection to come back. There's a blockWaitTime setting, but it apparently defaults to indefinite wait, and it isn't exposed in our config.
We should at least expose it via the Pool config schema that wraps the internal VT pool, and use a better default, or perhaps use different defaults based on whether a hard or soft pool is used?
Daniel also mentioned changing the VT library to throw an exception out if the minimum number of connections can't be set up in the pool.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list