Re: JDBC broken connection against Postgres 8.4

> As you see below, something seems....whacked. A simple loop with an
> unpooled connection (code provided below) often gives an exception
> when connecting. The Thread.sleep statement has been made as high as
> 5000 ms, and exceptions still sporadically occur.
>
> I don't know if this is a JDBC driver issue or core server issue. Or
> something here. But the code is so simple....
>
> Single box test (client, server on same machine, accessing 127.0.0.1)
> Postgesql 8.4.01
> JDBC3 8.4.701 (also tried 8.3.603)
> Sun JDK 1.5_16
> Windows XP SP3, 2GB RAM, 64MB-1GB heap
>
> Exception in thread "main" org.postgresql.util.PSQLException: The
> connection attempt failed.
> at
> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:137)
> at
> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
> at
> org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:124)
> at
> org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
> at
> org.postgresql.jdbc3.Jdbc3Connection.<init>(Jdbc3Connection.java:24)
> at org.postgresql.Driver.makeConnection(Driver.java:386)
> at org.postgresql.Driver.connect(Driver.java:260)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at com.gwava.db.DerbyConnectionPool.main(DerbyConnectionPool.java:193)
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(Unknown Source)

>
> I'm unable to reproduce the exception on a common client with the two
> PostgreSQL 8.3.x database configurations, one local the other on the
> network, listed below.
>
> All linux configurations
>
> Client:
>
> java version "1.5.0_12"
> jdbc version: "postgresql-8.3-603"
>
> Database Hosts:
>
> Host: 127.0.0.1
> -- Generated On: 2009.08.17 AD at 09:24:16 MDT
> -- SQL version: PostgreSQL 8.3.3
> -- Database: world
>
> -- Host: cindy.dandymadeproductions.net
> -- Generated On: 2009.08.17 AD at 09:10:41 MDT
> -- SQL version: PostgreSQL 8.3.0
> -- Database: world
>
> danap
>
> 2009/8/17 Michael Bell <mikebell90(at)yahoo(dot)com>
>
> I am not surprised. I strongly suspect this is an issue with
> Windows/PostgresSQL. OTOH, I did most of my testing against Postgres 8.4
> server.

I'm still unable to reproduce the exception on the given configuration
when the JDBC has
been upgraded to postgresql-8.4-701.jdbc3. I will upgrade to PostgreSQL
8.4 tomorrow,
been meaning to, on one of the systems and try again. I realize you are
talking about 8.4
and what I was trying to do is provide an elimination of one or more
variables to isolate
the problem, so the experts here could focus, which I believe they may
have already done. I
also understand that mine are Linux and your is windows and you believe
there lies the possible
whack so to speak. Couple of things though:

1. The original test code you provided I believe is not doing exactly
what you think. con is never
NULL besides the first time through the loop, which the test to
close the connection is taking
place no matter whether a connection was established or not. You
always close the connection,
Suggest you try:

} finally {
if (con != null)
{
con.close();
con = null;
}

I know this is probably be nothing, but your code is just not doing
what you set it up to do.

2. If you say your connection is not pooled, why in your original
exception trace, quoted above, is:

-> at com.gwava.db.DerbyConnectionPool.main(DerbyConnectionPool.java:193)

danap