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