On 02/02/2011 06:53, Rhonny David wrote: > Dear All, > > We are facing connection pool busy problem in tomcat 6.0.29. Till we finalize > our investigation, we need connection pool to be refreshed before all > connections get busy. Say for example if we have connection pool size 60, > then > it should get refresh when 15 connections get busy. We know that we cannot > define connection pool should refresh after X connections get busy but we can > at > least define the timeout for an abandoned connections. We have tried this > using > the removeAbandonedTimeout property, but still its behaviour is that it > refreshes the pool when all connections get busy. Following is the entry of > our > context.xml file: > > > <Resource factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory" > auth="Application" removeAbandoned="true" logAbandoned="true" > removeAbandonedTimeout="120" validationQuery="select 1" > driverClassName="net.sourceforge.jtds.jdbc.Driver" maxActive="60" > maxIdle="20" > maxWait="10000" name="DB_Pool" type="javax.sql.DataSource" > url="jdbc:jtds:sqlserver://10.22.4.30/XYZ" /> > > > Can anyone help how we can achieve this , that connection pool refreshes > before > all connections get busy?
Does your application have a connection leak? p
0x62590808.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
