db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Eade <se...@backstagetech.com.au>
Subject Re: running out of connections w/ postgresql
Date Wed, 05 Nov 2003 04:48:42 GMT
I cannot promise that I can help solve your problem, but it will help
generally if you can provide the contents of your Torque.properties
file.  The unit test may also be useful - it can't hurt to post it.

On commons-dev there was a thread about running out of connections
when mixing versions of dbcp and pool so it is worth double checking
that there are no old versions laying around causing problems.


Scott Eade
Backstage Technologies Pty. Ltd.

Justin Wood wrote:

>I don't know how far you've moved on this thing since Friday but I have 
>replaced my DBCP and Pool with versions 1.1 and still have the problem and I 
>am using Torque 3.1 .   I have a JUnit test that tests to failure if you 
>would like me to send it to you.   I just run it out of ant  lots of times 
>(>32) till it falls over at the 32nd time.  The max number of connections 
>allowed by default by prostgres is 32.   
>Are there any Torque developers out there that can give us some help before we 
>get our hands dirty with the source?

To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

View raw message