| From: | Jan de Visser <jdevisser(at)digitalfairway(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Cc: | "Paul Tomblin" <ptomblin(at)gmail(dot)com> |
| Subject: | Re: Getting "This ResultSet is closed" exceptions |
| Date: | 2008-02-19 01:17:58 |
| Message-ID: | 200802182017.58477.jdevisser@digitalfairway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Monday 18 February 2008 18:07:59 Paul Tomblin wrote:
> I've turned off autocommit, and am
> running around the code trying to figure out where is the best place
> to put "conn.commit();" calls.
Come again? You are using a single connection and are calling commit and
seemingly random spots? That means that thread A will call commit while
thread B is in the middle of doing things.
You are applying liberal amounts of lipstick on an animal that to everybody
looks conspicuously like a porcine. Do yourself a favour. Introduce a
connection pool before you (or worse, your customers) go insane.
jan
--
--------------------------------------------------------------
Jan de Visser jdevisser(at)digitalfairway(dot)com
Baruk Khazad! Khazad ai-menu!
--------------------------------------------------------------
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-19 01:20:54 | Re: Implementing setQueryTimeout() |
| Previous Message | Oliver Jowett | 2008-02-19 01:01:34 | Re: Implementing setQueryTimeout() |