2016-02-11 1:38 GMT+01:00 Shawn McKinney <[email protected]>:
>
> > On Feb 10, 2016, at 8:29 AM, Jan Sindberg <[email protected]> wrote:
> >
> > Summary:
> > If we configure "testWhileIdle" and " timeBetweenEvictionRunsMillis" it
> should activate the LookupLdapConnectionValidator and reduce the issue. We
> should as well consider the other pool-settings for appropriate defaults.
>
> Jan, we need test case(s) to illustrate these fault conditions. Doesn’t
> have to be a junit test necessarily, but a set of steps that can be
> verified - somehow. After that we’ll create a JIRA ticket and go from
> there.
>
> Thanks,
>
> Shawn
The test case, roughly;
Set up a commander connected to ApacheDS. Log in and refresh a lot to
activate a couple of connections. Log out and let it run over night. When
you log in the next day, you will see the delay.
We have applied the following in ApacheDsDataProvider:
adminPool.setTestWhileIdle(true);
adminPool.setTimeBetweenEvictionRunsMillis(1000 * 60 * 30);
...
userPool.setTestWhileIdle(true);
userPool.setTimeBetweenEvictionRunsMillis(1000*60*30);
...
logPool.setTestWhileIdle(true);
logPool.setTimeBetweenEvictionRunsMillis(1000 * 60 * 30);
Every 30 minutes this will test three (3 is default) idle threads and evict
them if they fail an attempt of a simple lookup on the rootDSE.
I have not yet established how long time it takes before a connection is
stale
I hope 30 minutes is enough - I suspect that the test will keep the
connections alive if the time is too short.
// Jan
