Dear All,=0A=0AWe are facing connection pool=A0busy problem in tomcat 6.0.2=
9. Till we finalize =0Aour investigation, we need=A0connection pool to be r=
efreshed before all =0Aconnections get busy. Say for example if we have con=
nection pool size 60, then =0Ait should get refresh when=A015 connections g=
et busy. We know that we cannot =0Adefine connection pool should refresh af=
ter X connections get busy but we can at =0Aleast define the timeout for an=
abandoned connections. We have tried this using =0Athe removeAbandonedTime=
out property, but still its behaviour is that it =0Arefreshes the pool when=
all connections get busy. Following is the entry of our =0Acontext.xml fil=
e:=0A=0A=0A<Resource factory=3D"org.apache.tomcat.dbcp.dbcp.BasicDataSource=
Factory" =0Aauth=3D"Application" removeAbandoned=3D"true" logAbandoned=3D"t=
rue" =0AremoveAbandonedTimeout=3D"120"=A0validationQuery=3D"select 1" =0Adr=
iverClassName=3D"net.sourceforge.jtds.jdbc.Driver" maxActive=3D"60" maxIdle=
=3D"20" =0AmaxWait=3D"10000" name=3D"DB_Pool" type=3D"javax.sql.DataSource"=
=A0 =0Aurl=3D"jdbc:jtds:sqlserver://10.22.4.30/XYZ" />=0A=0A=0ACan anyone h=
elp how we can achieve this , that connection pool refreshes before =0Aall =
connections get busy?=0A=0ARegards,=0ADavid=0A=0A=0A=0A
|