IdPv3 reload-service.sh and existing LDAP pool

[Scott Koranda]

> On 9/14/16, 2:41 PM, "users on behalf of Scott Koranda" <users-bounces at shibboleth.net on behalf of skoranda at gmail.com> wrote:
> 
> > will the existing pool of LDAP connections be "torn down" and
> >    new connections created with the new value for baseDN?
> 
> That would be my expectation/assumption. All the objects defined in that Spring context are being created and then swapped in behind a single synchronized service facade.
> 
> However, I think we've noted that we're not reloading
> properties, so you couldn't effect such a change unless the
> baseDN were inline.

The essential configuration in attribute-resolver.xml is

<resolver:DataConnector id="myLDAP" xsi:type="dc:LDAPDirectory"
        ldapURL="ldap://myserver"
        baseDN="dc=myorg,dc=org"
        connectionStrategy="ACTIVE_PASSIVE"
        searchScope="SUBTREE" >
        <dc:FilterTemplate>
            <![CDATA[
                (uid=$resolutionContext.principal)
            ]]>
        </dc:FilterTemplate>
</resolver:DataConnector>

so I think that is "inline".

I am not seeing the expected changes after the reload but I am not
confident there is not another issue. 

Thanks,

Scott K