From: | Art Gramlich <art(dot)gramlich(at)healthtrio(dot)com> |
---|---|
To: | Toru SHIMOGAKI <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Patch to add a socketTimeout property. |
Date: | 2008-04-10 16:50:55 |
Message-ID: | 9947D704-EED3-4A09-AE11-D899E4776CCB@healthtrio.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hopefully, it will work for your problem also. We access several
remote databases on the other side of a vpn and network problems used
to cause a lot of issues. With some other drivers, we have been able
to set this property and when these occur, flag in our connection
pools that there are network problems and shut them down until the
problem is corrected.
Art Gramlich
Chief Application Architect
HealthTrio, LLC
art(dot)gramlich(at)healthtrio(dot)com
On Apr 9, 2008, at 9:36 PM, 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.
>
> [1] http://archives.postgresql.org/pgsql-jdbc/2008-02/msg00022.php
>
> Best regards,
>
> --
> Toru SHIMOGAKI<shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp>
> NTT Open Source Software Center
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2008-04-10 18:31:26 | Re: Patch to add a socketTimeout property. |
Previous Message | Thomas Burdairon | 2008-04-10 12:33:39 | Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work |