Hello!
Thank you very much for this hint - there is indeed a firewall between this in-house appserver and the DB - and that's
beenbugging me personally for ages, since idle PGAdminII-connects would be closed without notice, too, which causes
longtimeout-waits in PGAdminII and forces me to restart the connection. This might be the cause for this issue, too -
andthe admin of our inhouse network seems to be unable to resolve this firewall-behaviour. I'll try and see if it
changesanything, if I switch off of the connection-persitancy ("Maintain connections across client requests").
Thanks again for your help!
Kind regards
Markus
> -----Ursprüngliche Nachricht-----
> Von: Oliver Jowett [mailto:oliver@opencloud.com]
> Gesendet: Donnerstag, 2. Dezember 2004 22:26
> An: Markus Wollny
> Cc: pgsql-jdbc@postgresql.org
> Betreff: Re: [JDBC] java.net.SocketException: Connection
> reset by peer: socket write error
>
> 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
>