Re: Patch to add a socketTimeout property. - Mailing list pgsql-jdbc

From Art Gramlich
Subject Re: Patch to add a socketTimeout property.
Date
Msg-id 5B7662E7-FE50-40C5-B1F3-0D01EB08F6BF@healthtrio.com
Whole thread Raw
In response to Re: Patch to add a socketTimeout property.  (Kris Jurka <books@ejurka.com>)
Responses Re: Patch to add a socketTimeout property.  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
They do.  We usually have different connection pools for normal (short
running) and long queries.  Since almost all are short running, this
has worked well for us.  I actually haven't tried setting keepalive in
this situation. so I can't say much, but the vpn solutions we have
used have at times gotten into some pretty wierd states and sotimeouts
could stop our pools from going crazy.



Art Gramlich
Chief Application Architect
HealthTrio, LLC
art.gramlich@healthtrio.com

On Apr 10, 2008, at 11:31 AM, Kris Jurka wrote:

>
>
> On Thu, 10 Apr 2008, Toru SHIMOGAKI wrote:
>
>>
>> Art Gramlich wrote:
>>> Several jdbc drivers have recently added a way to set  the
>>> SOTimeout on the connections socket.  For those of us accessing
>>> databases over a unreliable connections, this can be quite helpful.
>>
>> Good. Although I submitted setKeepAlive patch to solve network down
>> two month ago[1], it is not accepted so far. I think socket timeout
>> is reasonable solution and easy to use.
>>
>
> It seems like keepalives are a better solution to dead server
> detection.  Don't timeouts just cause problems when you have a long
> running query?
>
> Kris Jurka


pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Patch to add a socketTimeout property.
Next
From: Panagiotis Papadakos
Date:
Subject: Problem with very big queries.