Shibboleth IdP v4.0.1 and too many LDAP connections ESTABLISHED

[Cantor, Scott]

If you're talking about reloading the resolver service, I'm not aware of any cases where it would hold on to the old connections unless you're doing something unsupported like rolling it back to using JNDI as an LDAP provider, which still causes socket leaks in some JVMs. V4 defaults to the UnboundID LDAP client and it doesn't leak like that.

-- Scott