current community

your communities

more stack exchange communities

Stack Exchange
tour help
careers 2.0
Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 2 down vote favorite

So, I got this problem. I'm using JDBC, and every time if query get SQL exception and I/O error, the connection to pgsql database will be dropped automatically.

As a result, I have to check if the connection is open before every query, and if it's not open, I'll open it again.

Anyone knows why this is happening?

Also I know even I give perfect connection parameters, the connection could randomly drop.

Anyone knows how to set connection parameter to auto-check connections and reopen it in case connections down?

Currently I'm not using connection pooling.

Following is my code to set connection properties:

Properties pgsqlInfo = new Properties();
pgsqlInfo.setProperty("user", userName);
pgsqlInfo.setProperty("password", password);
pgsqlInfo.setProperty("ssl", "true");
pgsqlInfo.setProperty("loginTimeout", "0");
pgsqlInfo.setProperty("tcpKeepAlive", "true");
pgsqlInfo.setProperty("socketTimeout", "0");

con = (Connection) DriverManager.getConnection(url + "/" + dbName, pgsqlInfo);
share|improve this question
    
I found this resource which may help you solve your problem: groups.google.com/forum/#!topic/pgsql.interfaces.jdbc/… –  Thomas Langston Jun 26 '13 at 18:28
    
@ThomasLangston ths link is about connections timing out, regardless of query exceptions –  Oleg Mikheev Jun 26 '13 at 18:32
    
please provide the code and exception –  Oleg Mikheev Jun 26 '13 at 18:33
    
I/O error doesn't seem to be a SQL problem. It looks such as connection timeout or something so on. Also probably SQLException can be the final expcetion with its IO error as a reason. Please provide more information about it: how you create the connection, the code you run (statement/prepared statement/callable statement), full stack trace, probably the postgresql.conf too –  Martin Strejc Jun 26 '13 at 18:48
    
You guys are right, I think this may be caused by timeout. I showed my settings above. Any suggestions? –  Hao Huang Jun 26 '13 at 21:16

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.