hi andrus, thank you for your reply, but we are experiencing "idle in transaction" connections that are hung and have to be killed manually. there are a lot of other connections in state "idle" which we recognized as the connection-pool. so we are already worrying ;-). we have a lot of background/scheduled tasks in our app, so we dont really know where the problem occurs. currently we are searching our logs to find something usefull.
kind regards, peter -----Ursprüngliche Nachricht----- Von: Andrus Adamchik [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 3. April 2007 18:27 An: [email protected] Betreff: Re: postgres, idle in transaction 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 >
