Re: Detecting 'socket errors' - closing the Connection object

From: Dmitry Tkach <dmitry(at)openratings(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: David Wall <d(dot)wall(at)computer(dot)org>, pgsql-jdbc-list <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Detecting 'socket errors' - closing the Connection object
Date: 2003-07-22 14:18:28
Message-ID: 3F1D47B4.5030804@openratings.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

>
>
>Unfortunately the isClosed() javadoc is fairly explicit in saying you can't
>use it for this:
>
> Retrieves whether this Connection object has been closed. A connection is
> closed if the method close has been called on it or if certain fatal errors
> have occurred.
>
Hmmm.... To me this phrase sounds like exactly what he was asking for...
Perhaps, it would then make sense to make isClosed() return false if the
socket goes south...
I think that situation very well qualifies as a 'certain fatal error'
after all...

>This method is guaranteed to return true only when it is
> called after the method Connection.close has been called.
>
>
This is weird.... direct contradiction with the previous sentense isn't
it? :-)

Dima

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Felipe Schnack 2003-07-22 14:20:11 Re: patch: tiny patch to correct stringbuffer size estimate
Previous Message Oliver Jowett 2003-07-22 14:17:09 patch: support user implementations of Array in setArray()