I have been using those values with the SharedPoolDataSourceFactory.
Perhaps your version of the dbcp is older than the one we are using and
doesn't support these settings? We are using commons-dbcp-1.2.1.jar -
perhaps you could get a newer one and see if that works.
Ian
On Sep 24, 2004, at 3:48 PM, T E Schmitz wrote:
Hello Ian,
Ian Ragsdale wrote:
We recently had a similar problem. Here's what we did, which
appeared to alleviate the problem without addressing the underlying
connection leak:
# don't wait indefinitely for a connection
torque.dsfactory.scimitar.pool.maxWait = 5000
# allow up to 25 connections in the pool (up from 8)
torque.dsfactory.scimitar.pool.maxActive = 25
# remove connections that have been abandoned
torque.dsfactory.scimitar.pool.removeAbandoned = true
When I set any of these properties (maxWait, maxActive,
removeAbandoned, logAbandoned), I get an error:
Category:org.apache.torque.dsfactory.AbstractDataSourceFactory
Message:Property: maxActive value: 10 is not supported by DataSource:
org.apache.commons.dbcp.datasources.PerUserPoolDataSource
and so forth.
I had the same problems with SharedPoolDataSourceFactory
Hence I have not played around with these settings any further.
Does anybody understand which properties are available when?
--
Regards/Gru�,
Tarlika Elisabeth Schmitz
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
