[JIRA] Closed: (SC-173) LdapPoolEmptyStrategy should check that a connection to the LDAP server can be established during its initialization

[Chad La Joie (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SC-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chad La Joie closed SC-173.
---------------------------

    Resolution: Fixed

Done in rev 1015

> LdapPoolEmptyStrategy should check that a connection to the LDAP server can be established during its initialization
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: SC-173
>                 URL: https://issues.shibboleth.net/jira/browse/SC-173
>             Project: Shibboleth Common - Java
>          Issue Type: Improvement
>          Components: Attribute Authority
>    Affects Versions: 1.3.4
>            Reporter: Chad La Joie
>            Assignee: Chad La Joie
>            Priority: Minor
>             Fix For: 1.3.5
>
>
> There are two pooling strategies for the LDAP data connector.  A no-op one, called LdapPoolEmptyStrategy, and one that actually performs pooling called LdapPoolVTStrategy.  The later implicitly checks that the LDAP server can be reached and so if the LDAP configuration is wrong it fails immediately.  The former however does not do this and so doesn't fail until its used.
> Have LdapPoolEmptyStrategy check that it can reach the LDAP at startup time so that it fails in the same as the other pooling strategy if the configuration is wrong (or if the LDAP server is down).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira