I'm (still) trying to figure out a problem with our connection pool locking
up - all threads waiting for a connection from the DBCP pool, such as
following from a thread dump:
...
"Thread-28" daemon prio=1 tid=0xac9dedc8 nid=0x5256 waiting for monitor
entry [0xb0607000..0xb0608580]
at
org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool
.java:111)
- waiting to lock <0x4a26b950> (a
org.apache.commons.dbcp.AbandonedObjectPool)
at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.ja
va:110)
at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:3
12)
at com.acme.Connector.CreateConnection(Connector.java:56)
...
I set DBCP connection parameters as follows, expecting to always see a
minimum of 10 idle connections. But when I look at MySQL (4.0.18) I only see
1 or 2 connections. What gives, does minIdle not work as I am expecting?
Thank you - Richard
...
<Resource name="jdbc/firedrumarketing.com" auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/firedrummarketing.com">
<parameter>
<name>url</name>
...
<parameter>
<name>removeAbandoned</name>
<value>true</value>
</parameter>
<parameter>
<name>removeAbandonedTimeout</name>
<value>60</value>
</parameter>
<parameter>
<name>logAbandoned</name>
<value>true</value>
</parameter>
<!-- 2006/04/18 Richard Mixon, changes to avoid firedrummarket.com lockups
-->
<!-- Explicitly stating pool sizes and values, rather than defaulting to
unlimited -->
<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>30000</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>30</value>
</parameter>
<parameter>
<name>minIdle</name>
<value>10</value>
</parameter>
</ResourceParams>
...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
