From: | Jeffrey Tenny <jeffrey(dot)tenny(at)comcast(dot)net> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: "Idle in Transaction" revisited. |
Date: | 2004-09-21 01:21:49 |
Message-ID: | 414F822D.3020403@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> Trouble is, with JDBC as its currently implemented, the instant you
> Commit() or Rollback(), JDBC starts a new transaction automatically,
> since JDBC has no explicit Begin(). If that thread then goes
> quiescent for an arbitrary period of time (perhaps waiting for more
> messaging traffic, our apps are message driven factory floor
> middleware things), this transaction remains open. Our
> applications are characterized by bursts of frenetic activity
> followed by long idle periods, quite unpredictably.
I was under the impression that this was easily addressed by
delaying the onset of the next transaction after commit/rollback until
some actual statement activity began. (like a SELECT...)
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-09-21 01:50:00 | Re: Auto-increment serial (Postgresql JDBC driver w/ |
Previous Message | Francisco Figueiredo Jr. | 2004-09-21 00:19:35 | Re: Returning just one resultset from function call with refcursor |