Re: Threading problem

From: Palle Girgensohn <girgen(at)pingpong(dot)net>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Threading problem
Date: 2005-04-22 22:11:51
Message-ID: 56E92D14DA3B1D802F4E2BD0@palle.girgensohn.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

--On lördag, april 23, 2005 10.08.12 +1200 Oliver Jowett
<oliver(at)opencloud(dot)com> wrote:

> Palle Girgensohn wrote:
>
>> First, we cannot see anything in our code that would offer the
>> possibility for two threads to get hold of the same postgresql
>> connection. There might be something we're missing, but the only changes
>> made from a working system is updates of postgresql and its JDBC driver,
>> so it's easy to suspect a bug in the jdbc driver...
>
> There's really no shared state between different connections -- they're
> each independent objects with their own protocol layer objects, TCP
> connection etc. So it's hard to see how there could be a bug where two
> different Connection objects end up using the same physical connection..
> I'd be more suspicious of your application or connection pool.

Honestly, so am I. Only some change in pg 8 or pg-jdbc-8.0 triggered the
problem. It has worked like a charm for ages before this upgrade. Still,
you're probably right, I'll have to find the problem in our own code.

/Palle

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Palle Girgensohn 2005-04-22 22:13:08 Re: BUG? res.next() == false, but psql finds tuples?
Previous Message Oliver Jowett 2005-04-22 22:10:28 Re: BUG? res.next() == false, but psql finds tuples?