Per last comment from the link you posted:
"The 'idle' processes are correct behavior; they are the shared
persistent connections to the database the connection pool leaves
open to accelerate database access. Only when you have hanging 'idle
in transaction' threads do you have a problem, as those consume
connections permanently since they are hung processes and are not
shared."
I think that's what you are seeing - the active connection pool. No
need to worry unless your app starts hanging, or the pool size starts
unexpectedly going up.
Andrus
On Apr 3, 2007, at 2:57 AM, Peter Schröder wrote:
hi there,
we have some trouble with our postgres database using cayenne. our
application is not writing any data to the db, there is only read-
statements. nevertheless we have some connections in "idle in
transaction" state, wich indicates some transactions not beeing
properly closed.
i found a link about hibernate and this issue:
http://www.ashtech.net/~syntax/blog/archives/56-Hibernate-and-
PostgreSQL-Require-Transactions.html
is there a similar approach to this for cayenne?
kind regards,
peter
