Hi Ilan,
I had exactly the same problem several months ago with PostgreSQL and
Torque. I *think* I had to change the dsfactory inside my
conf/torque.properties file to read:
torque.dsfactory.eCommerce.factory =
org.apache.torque.dsfactory.SharedPoolDataSourceFactory
You should keep the property name though, the "eCommerce" above is the
name for my project. As I remember, doing this solved the problem. It's
been a long time, so I may be forgetting something important here.
I also turned off the torque's idbroker and it's "usenewconnection"
option and upgraded to use the latest postgres jdbc driver. I found
there are problems when using Postgres 8 with a version 7 driver as I
was doing before.
I think you are on the right track, I used to have 100 idle connections
to the DB and had to restart the app server every day until I found the
fix. Too bad I can't remember exactly what I did back then.
Paulo
Peter Courcoux wrote:
Hi Ilan,
It is a long time since I have hit a problem like this but I seem to
recall that when my postgresql db ran out of connections it was clear
from the process listing, (ps aux) that the database connections were
not being released.
Peter
Ilan Azbel wrote:
Hello,
I have a Linux turbine server using torque for db connections. Once in a
while it just stops serving pages and needs to be restarted - the
process is
running but seems to be dead.
I am suspecting the db connection pool runs out of connections. Is
there any
diagnostic tool available, or a technique I can use to see how my torque
connection pool is doing? Maybe I'm on the wrong track, maybe there
could be
other reasons.
Any help would be appreciated.
Ilan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
