Re: Removing our datasource/pooling implementation.

From: Kris Jurka <books(at)ejurka(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Removing our datasource/pooling implementation.
Date: 2005-01-11 22:53:30
Message-ID: Pine.BSO.4.56.0501111743320.28776@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, 12 Jan 2005, Oliver Jowett wrote:

> What needs fixing in our PooledConnection implementation? I can take a
> look at repairing whatever concerns you. I haven't noticed any problems
> myself, but our app hardly exercises the whole class..
>

First I don't use our PooledConnection and I'm also a little unclear on
whose resposibility (CPDS vs the actual pool) certain things are, so this
is just a combination of anecdotes and looking at the code. Nothing is
really broken for normal use, but when something goes wrong there is very
little error detection and fallback. Specifically when a connection to
the database server is lost via a server restart or even potentially user
level code Statement.execute("SET client_encoding TO 'LATIN1'); the dead
connection is not destroyed and will keep being given to clients.

Kris Jurka

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2005-01-11 22:56:47 Re: Postgres JDBC driver (80b1.308) bug
Previous Message Oliver Jowett 2005-01-11 22:06:14 Re: Removing our datasource/pooling implementation.