This is definitely not a problem with the server Tom Lane has told me
and I have verified the with my sources. It seems to be in the JDBC driver.
It only seems to happen when the JDBC client and the postgresql server
are on seperate machines and possibly on different networks.
I have further talked with the site where it happens and researched
the isClosed() JDBC call. The isClosed() call according to my sources
is only required to tell you if you have closed the connection not
if the connection has been closed by a timeout. The isClosed() call
in Oracle is non-functional about timeouts across a wan. I should have
read the JDBC spec and not just the documentation. I will not make that
same mistake again when it comes to JDBC.
I have verified that the connections stay active when the JDBC client and
the postgresql server are on the same machine. If your connections are
across a LAN and not the same machine then that would be helpful as I
will only have to research a problem with a wan and that might not be a problem
at all for my configuration. I will start my research with two machines on
the same LAN unless you can tell me that your configuration is across a LAN.
TIA for any info.
At 11:49 AM 2/1/2002 +0100, Stefano Reksten wrote:
>At 12.57 31/01/02 -0500, you wrote:
>>However, I'm not very familiar with Java and so I cannot dismiss the
>>possibility that some layer inside the JVM might take it upon itself
>>to close an open TCP connection after a period of inactivity.
>
>I have a Connection Pool active 365/24/7 on a site I manage, and the
>connections are opened, reused, but not closed, and I never had such a
>problem; HTH.
>
>>The pgsql-jdbc list might be a better place to ask if anyone knows of
>>such problems in a JDBC context. Not sure how many JDBC people read
>>pgsql-bugs.
>
>Well, at least one ;)
>
>Ciao,
> Stefano
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org