From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | anthony(at)webmediaworks(dot)co(dot)uk, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: An I/O error occured while sending to the backend |
Date: | 2005-04-06 17:35:52 |
Message-ID: | 1112808952.20921.42.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Wed, 2005-04-06 at 11:24, John R Pierce wrote:
> Anthony Chaffey wrote:
> > Hi,
> >
> >
> > I have developed an application using the postgresql-8.0-310.jdbc3
> > driver and connecting to a postgresql 8.0.1 database running on fedora
> > core 3. Everything was working fine until i started running the
> > application on the clients pc's. Randomly they receive an error, the
> > stack trace of which is below.
> >
> > The only difference between my testing pc and the client's pc's is that
> > they use a wireless network card. Both my machine and the client's pc's
> > are running Windows XP with SP2. Similar problems have been posted on
> > this mailing list and people have suggested a firewall is clearing the
> > connection which makes sense as the client claims this problem only
> > occurs if the application is left idle for a short time but does anyone
> > have any more information that may help?
>
> its probaly exactly what you say, most firewalls, NAT routers, etc will time
> out idle sockets after a certain number of minutes... They have to do this,
> otherwise the firewall's connection tracking tables will fill up with old flug.
>
> only good solution is to catch the exception, and attempt to reopen the
> database connection, and retry the operation....
Does setting a lower tcp_keepalive_time help these problems with NAT?
It certainly fixed the problems I've seen with non-NAT firewalls. (this
is a linux kernel setting, i'm sure there's an equivalent for other
unixes)
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2005-04-06 18:23:12 | Re: UNICODE encoding and jdbc related issues |
Previous Message | Chris Kratz | 2005-04-06 17:18:44 | UNICODE encoding and jdbc related issues |