Connection state after network failure?

From: "Kevin Birkett" <KBirkett(at)icudata(dot)com>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Connection state after network failure?
Date: 2007-02-09 19:10:14
Message-ID: 346FF8985107AA41AC92CEC80E21E6B5BBC7@phxx05.exchange.phxx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hello,

I'm having a problem with our software which uses Postgres 7.2.3 and the JDBC driver associated with it. In our code we only create one connection to the database, and then use that connection as needed for our DB interaction. The problem comes in when I simulate a network failure (yank the cat5) after the app has started up and connected to the remote database. I've tried an idea I found by searching the archives of this mailing list, but I haven't been able to get it to work.

My current technique is:

try {
con.createStatement().execute("Select 1");
} catch (Exception e) {
......
......
}

To me, if the connection loses its network connectivity, an exception should be thrown here, and then I can handle it. However, what actually happens is the system locks up on the call to execute and it never throws and exception or a returns value (since the network is unavailable). Am I missing something easy here? All I want to do is to check whether or not the connection is valid and available.

Thanks for any help you can give.

Kevin

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Chris Gamache 2007-02-09 22:15:09 stringtype=unspecified problem
Previous Message James Neff 2007-02-09 14:15:16 Re: use connection pooling