该异常表示泄漏数据库连接的应用程序代码的典型情况.您需要确保在正常的JDBC成语中以相同的方法块获取并关闭
try-with-resources块中的所有(Connection,Statement和ResultSet).
public void create(Entity entity) throws SQLException {
try (
Connection connection = dataSource.getConnection();
PreparedStatement statement = connection.prepareStatement(SQL_CREATE);
) {
statement.setSomeObject(1, entity.getSomeProperty());
// ...
statement.executeUpdate();
}
}
或者当您不在Java 7时,在try-finally块中.最终关闭它们将保证在异常情况下也关闭它们.
public void create(Entity entity) throws SQLException {
Connection connection = null;
PreparedStatement statement = null;
try {
connection = dataSource.getConnection();
statement = connection.prepareStatement(SQL_CREATE);
statement.setSomeObject(1, entity.getSomeProperty());
// ...
statement.executeUpdate();
} finally {
if (statement != null) try { statement.close(); } catch (SQLException logOrIgnore) {}
if (connection != null) try { connection.close(); } catch (SQLException logOrIgnore) {}
}
}
是的,即使使用连接池,您仍然需要自己关闭连接.这是起始者的一个常见错误,他们认为它会自动处理关闭.这不是真的.连接池即返回一个封装的连接,它在close()中执行以下操作:
public void close() throws SQLException {
if (this.connection is still eligible for reuse) {
do not close this.connection, but just return it to pool for reuse;
} else {
actually invoke this.connection.close();
}
}
不关闭它们将导致连接未被释放回池重新使用,因此它将一次又一次地获取一个新的连接,直到数据库用完,从而导致应用程序崩溃.
也可以看看: