For the record: The problem was (predictably) my code; I was missing a
line that should have stored the SessionFactory in the servlet context
- every attempt to obtain a session was obtaining a new factory, and
hence a new connection pool.
Thanks for the help all,
jim
On Sat, Jan 04, 2003 at 10:
I have never seen this problem (I test with Postgres 7.3 running under
cygwin), but I imagine that it is to do with how you have configured
connection pooling. You can set
hibernate.connection.pool_size=0
to disable pooling, if you like, or try out Juozas' suggestion and use a
different pooling
Try DBCPConnectionProvider.
- Original Message -
From: "Jim Downing" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 03, 2003 10:24 PM
Subject: [Hibernate] Postgres problem - idle in transaction.
> Hi all,
>
> I have a problem with
Hi all,
I have a problem with hibernate and postgresql that I suspect might be
related to Matt Raible's Oracle problems. Every time hibernate does
it's stuff to update the database, postgres spawns another "idle in
transaction" process. Eventually it gives up and the driver throws: -
Backend star
