Tom,
I tend to use the DBCP from apache over the SIMPLE one that we have included
in IBATIS. It does add one more jar to the pile but oh well :)
Here is a page that defines all of the parameters and what they do.
http://jakarta.apache.org/commons/dbcp/configuration.html
Here is the main DBCP page http://jakarta.apache.org/commons/dbcp/
I believe that both the developers manual and the IBATIS book cover how to
configure your transaction manager to use DBCP.
Nathan
On 2/22/07, Tom Henricksen <[EMAIL PROTECTED]> wrote:
We have a problem where we exceed our maximum connections on our
database. Our setup is here. Does MaximumIdleConnections mean that the
database right away grabs 25 connections? Or is that the maximum idle
connections before it starts to clean up?
I see in the iBatis-SqlMaps-2.pdf it says Pool.MaximumIdleConnections -
"The number of idle connections that will be stored in the pool." Is
that initially? Is there Pool.IntialSize?
<transactionManager type="JDBC">
<dataSource type="SIMPLE">
<property name="JDBC.Driver" value="${driver}"/>
<property name="JDBC.ConnectionURL"
value="${url}"/>
<property name="JDBC.Username"
value="${username}"/>
<property name="JDBC.Password"
value="${password}"/>
<property name="Pool.MaximumActiveConnections"
value="50"/>
<property name="Pool.MaximumIdleConnections"
value="25"/>
<property name="Pool.MaximumWait" value="600"/>
<property name="Pool.LogAbandoned"
value="true"/>
<property name="Pool.RemoveAbandoned"
value="true"/>
<property name="Pool.RemoveAbandonedTimeout"
value="50000"/>
<property name="Pool.PingQuery" value="select *
from sysibm.SYSDUMMY1"/>
<property name="Pool.PingEnabled" value="true"/>
<property name="Pool.PingConnectionsOlderThan"
value="600000"/>
<property name="Pool.PingConnectionsNotUsedFor"
value="600000"/>
</dataSource>
</transactionManager>
Thanks,
Tom
