Re: idle in transaction
| От | João Paulo Ribeiro |
|---|---|
| Тема | Re: idle in transaction |
| Дата | |
| Msg-id | 450E639B.5090605@mobicomp.com обсуждение исходный текст |
| Ответ на | idle in transaction ("Sriram Dandapani" <sdandapani@counterpane.com>) |
| Список | pgsql-jdbc |
Hi.
Are you using DODS/Enhydra to manage your database connection pool?
If yes, see my email in the Enhydra mailing list:
http://mail-archive.objectweb.org/dods/2006-05/msg00000.html
http://mail-archive.objectweb.org/dods/2006-06/msg00000.html
The latest DODS dont have this issue anymore. You just use "RollbackOnReset" option.
Bests regards.
João Paulo Ribeiro
Sriram Dandapani wrote:
Are you using DODS/Enhydra to manage your database connection pool?
If yes, see my email in the Enhydra mailing list:
http://mail-archive.objectweb.org/dods/2006-05/msg00000.html
http://mail-archive.objectweb.org/dods/2006-06/msg00000.html
The latest DODS dont have this issue anymore. You just use "RollbackOnReset" option.
Bests regards.
João Paulo Ribeiro
Sriram Dandapani wrote:
I use postgres 8.1.2 database and postgres 8.1.404 jdbc driver .
I keep seeing “idle in transaction” connections on the postgres box all the time. The application logic closes all connections , so it makes me wonder if the driver is issuing a begin statement after every commit to leave a floating transaction open.
This is causing autovacuum to not finish (and hence I have to frequently issue database-wide vacuums to prevent the transaction id wraparound problem)
Any help here is appreciated
Thanks
Sriram
-- João Paulo Ribeiro | Senior Software Engineer jp@mobicomp.com PHONE: + 351 253 305 250 FAX : + 351 253 305 250 www.mobicomp.com ________________________________________________________________ About Solutions | Wireless World CONFIDENTIALITY NOTICE: This message, as well as existing attached files, is confidential and intended exclusively for the individual(s) named as addressees. If you are not the intended recipient, you are kindly requested not to make any use whatsoever of its contents and to proceed to the destruction of the message, thereby notifying the sender. DISCLAIMER: The sender of this message can not ensure the security of its electronic transmission and consequently does not accept liability for any fact which may interfere with the integrity of its content.
В списке pgsql-jdbc по дате отправления: