| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: org.postgresql.util.PSQLException: The column name x was |
| Date: | 2005-06-16 21:53:20 |
| Message-ID: | 42B1F4D0.7060104@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Kevin Grittner wrote:
>
> Given the circumstances, it looks like some race
> condition between the multiple JDBC threads might be involved.
Seems unlikely -- the JDBC driver spawns no threads itself (except for
one at connection time if you specify a login timeout, but that's dead
by the time the connection is established) and the objects involved in a
connection should be entirely independent of objects in another connection.
I wonder if there is some cross-thread access to a particular connection
going on in your application. The JDBC spec says that the various
exposed objects should be individually threadsafe, but I'm not sure how
well we follow that.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Minal Aryamane | 2005-06-17 04:45:00 | Re: Postgresql-JDBC connectivity |
| Previous Message | Kevin Grittner | 2005-06-16 16:19:20 | org.postgresql.util.PSQLException: The column name x was not found in this ResultSet. |