From: | Håkon Hansen <hha(at)mkt(dot)no> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Problem with JDBCRealm in Tomcat |
Date: | 2002-07-26 13:40:43 |
Message-ID: | 200207261540.44090.hha@mkt.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi!
I'm getting 'Connection reset by peer' and 'Socket closed' errors using
JDBCRealm in a web application running on Tomcat 4.0.3.
I am using RedHat Linux 7.3 and Java 1.4, and connecting to a PostgreSQL 7.2
back-end running remotely on RedHat Linux 7.3. It seems to work fine for a
while, but after a while (typically the next day) the error will occur.
I am using the pgjdbc2.jar JDBC driver, which seemed to be the appropriate one
for my setup. I have looked at the Java source code of this driver, and it
seems that the error occurs within a synchronized block, after the SELECT
statement has been written to the stream (it shows up in the PostgreSQL
server's log, too) and while reading - or trying to read - the response.
Anybody have any clues as to what might be wrong? All help greatly
appreciated!
Yours,
Haakon Hansen
Norway
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2002-07-26 14:07:01 | Re: Problem with JDBCRealm in Tomcat |
Previous Message | Dave Cramer | 2002-07-26 13:13:39 | Re: PreparedStatement: setting column names dynamically |