| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Markus Wollny <Markus(dot)Wollny(at)computec(dot)de> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: java.net.SocketException: Connection reset by peer: socket |
| Date: | 2004-12-02 21:25:45 |
| Message-ID: | 41AF8859.2090702@opencloud.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Markus Wollny wrote:
> It seems
> that somewhere along the line, the Application Server just looses the
> connection to the database after about 2h17min total runtime of the
> batch.
> java.net.SocketException: Connection reset by peer: socket write error
> at java.net.SocketOutputStream.socketWrite0(Native Method)
Check for firewalls between the appserver and the database server. The
error is a TCP-level connection error that means that the peer (the
database server) unexpectedly disappeared on us, and we didn't see an
orderly shutdown of the connection. If it always happens after a certain
connection length, or after the connection has been idle for a certain
period, it's likely that there is a stateful firewall in the way that is
dropping the connection after that period.
Failing that, does the database side log anything about the disconnection?
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Iain | 2004-12-03 03:13:13 | meta data information returned for domains |
| Previous Message | Oliver Jowett | 2004-12-02 21:20:39 | Re: Bug in setFetchSize |