You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2014/08/11 04:36:11 UTC
[Bug 56837] New: if validationQuery have error with
timeBetweenEvictionRunsMillis option, connection pool increase keep going
https://issues.apache.org/bugzilla/show_bug.cgi?id=56837
Bug ID: 56837
Summary: if validationQuery have error with
timeBetweenEvictionRunsMillis option, connection pool
increase keep going
Product: Tomcat Modules
Version: unspecified
Hardware: HP
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: jdbc-pool
Assignee: dev@tomcat.apache.org
Reporter: gap75@hotmail.com
ENV:
apache-tomcat-7.0.54
CentOS release 6.5 (Final)
jdk1.7.0_55
in case of setting the "timeBetweenEvictionRunsMillis",
when validationQuery is error, connection pool increase keep going.
Even if you set the maximum value(maxActive).
1. setting
<Resource
name="jdbc/PPAS_DS"
type="javax.sql.DataSource"
minIdle="2"
initialSize="3"
maxActive="6"
timeBetweenEvictionRunsMillis="20000"
username="xxx"
validationQuery="select1 12 "
driverClassName="org.postgresql.Driver"
password="xxx"
url="jdbc:postgresql://localhost:5432/postgres"/>
2. try to ues connection Pool
--> validationQuery error
-------------------------------------------------------
3. server connection increases after 20000 Millis
(timeBetweenEvictionRunsMillis value)
netstat -nap | grep 5432 | grep EST | grep java | wc -l
6
netstat -nap | grep 5432 | grep EST | grep java | wc -l
8
-------------------------------------------------------
If Pool can not guarantee maxActive value, that is problem.
Did I something wrong use timeBetweenEvictionRunsMillis option?
timeBetweenEvictionRunsMillis option is not available?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org