Robert, it should say, if you set a positive value, the value should not be
less than 1000ms. Otherwise you are hammering the system with eviction
checks.
Setting the value to 0, disables the check all together. There are other
ways to disable the same check by setting other flags,
918 @Override 919 public boolean isPoolSweeperEnabled() { 920 boolean timer
= getTimeBetweenEvictionRunsMillis()>0; 921 boolean result = timer && (
isRemoveAbandoned() && getRemoveAbandonedTimeout()>0); 922 result = result
|| (timer && getSuspectTimeout()>0); 923 result = result || (timer &&
isTestWhileIdle() && getValidationQuery()!=null); 924 result = result || (
timer && getMinEvictableIdleTimeMillis()>0); 925 return result; 926 }
On Fri, Jan 30, 2015 at 11:17 AM, Robert Anderson <ranom...@gmail.com>
wrote:
> Sorry,
>
> [1] https://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html
>
> 2015-01-30 15:15 GMT-03:00 Robert Anderson <ranom...@gmail.com>:
>
> > Filip,
> >
> > however, disabling the pool cleaner it should yield better results.
> >
> > The documention[1] says:
> >
> > "This value should not be set under 1 second"
> >
> > Isn't true?
> >
> >
> >
> > 2015-01-30 15:07 GMT-03:00 Filip Hanik <fi...@hanik.com>:
> >
> > Looking at the locks that are involved in the dead lock, it's all in the
> >> intersys traces. Furthermore, it seems as intersys may already be doing
> >> pooling inside the driver. If that is the case, you have two options
> >>
> >> 1. disable pooling in intersys OR
> >> 2. don't use tomcat's jdbc pool since intersys already does pooling
> >>
> >> however, disabling the pool cleaner it should yield better results.
> >>
> >> On Fri, Jan 30, 2015 at 11:02 AM, Filip Hanik <fi...@hanik.com> wrote:
> >>
> >> > Disable the pool cleaner
> >> >
> >> > timeBetweenEvictionRunsMillis=0
> >> >
> >> >
> >> >
> >>
> >
> >
>
