Default LDAP connection pool properties ?

[Cantor, Scott]

On 9/13/16, 11:32 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:

>    Sorry, we don’t “require" a duration. If it's a long we pass it along and log to INFO
> to use a duration instead. But only a duration and not a long actually works. So, yes, I
> guess that’s the bug. Maybe it will be obvious to Rod in the LDAP DC parser (the
> expirationTime property of the connection pool).

I don't see a bug in the code. It passes the value into a factory bean method called buildDuration that's used to pass either a long or a Duration into Spring and get back a long, and then the long is passed into the builder for the Ldaptive IdlePruneStrategy object.

That's basically the pattern we use for any cases where a Duration is supported by us, but not the underlying object(s).

But it should still support a long, so something's up.

-- Scott