Filip,
timeBetweenEvictionRunsMillis=0 does not disable PoolCleaner [1].
if (sleepTime <= 0) {
log.warn("Database connection pool evicter thread
interval is set to 0, defaulting to 30 seconds");
this.sleepTime = 1000 * 30;
} else if (sleepTime < 1000) {
log.warn("Database connection pool evicter thread
interval is set to lower than 1 second.");
}
[1]http://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java
2015-01-30 15:17 GMT-03:00 Robert Anderson <ranom...@gmail.com>:
> 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
>>> >
>>> >
>>> >
>>>
>>
>>
>
