在论坛上看到个帖子(http://bbs.csdn.net/topics/360264783),大致内容是finally块里"con=null"这条语句是否有意义。
在结合各位大牛的意见,再加上自己的实验之后,做了下猜想
首先,代码如下
public void testClose(Connection con) {
try {
if (con != null && !con.isClosed()) {
con.close();
}
} catch (SQLException e) {
e.printStackTrace();
} finally {
con = null;<span style="white-space:pre"> </span>//这里是否有必要
}
}
比如这种情况。将con指向null,三个目的:1.加快GC回收。2.防止出现异常,导致con没有成功关闭,这个时候在finally里定为null。3.多线程考虑(这点不清楚)一点一点谈:1.首先,我对GC的回收机制不是很清楚也查过一些资料。猜想这里con=null,有可能想回收的资源有两个:
1).调用这个方法的时候,将作为参数传入的连接(假定为con1)关闭。但是这样做是达不了目的的。con1作为参数传入testClose,方法里的con指向rs1。之后con=null,这条语句,并非是把con1指向null,而仅仅是将con指向null而已,而con1仍然是指向的Connection实例。在这个方法外,其他所有指向con1所指向的Connection实例的地方(例如在另外的地方,有引用b指向con1所指向的Connection实例),仍然是指向con1所指向的实例而并非是指向null。
(关于对象引用及赋值的问题,请看http://www.cnblogs.com/focusChen/articles/2497768.html)
2).另外,如果是单纯想把con回收,就更没必要了,因为出了这个方法之后,con离开他的作用域,GC会回收。2.同理,将con=null在出现异常的时候,将其=null,也并不会影响到con1。
3.多线程这块
以下是我写的测试代码</pre><p><pre name="code" class="java">package com.cqgs.test;
import java.beans.PropertyVetoException;
import java.sql.Connection;
import java.sql.SQLException;
import com.mchange.v2.c3p0.ComboPooledDataSource;
public class GCTest {
public static void main(String args[]) {
ComboPooledDataSource cpds = new ComboPooledDataSource();
try {
cpds.setDriverClass("com.mysql.jdbc.Driver");
} catch (PropertyVetoException e2) {
e2.printStackTrace();
}
cpds.setJdbcUrl("jdbc:mysql://localhost:3306/TESTGC");
cpds.setUser("root");
cpds.setPassword("root");
cpds.setMaxPoolSize(200);
cpds.setMinPoolSize(20);
Connection con1 = null;
try {
con1 = cpds.getConnection();
} catch (SQLException e1) {
e1.printStackTrace();
}
GCTest t = new GCTest();
for (int i = 0; i < 5; i++) {
System.out.println("i = " + i);
t.testClose(con1);
System.out.println("con1 = " + con1);<span style="white-space:pre"> </span>//在执行testClose之后,查看con1是否为null
try {
if (con1!=null && con1.isClosed()) {
System.out.println("con1 is closed");<span style="white-space:pre"> </span>//con1是否已关闭
}
} catch (SQLException e) {
e.printStackTrace();
}
}
}
public void testClose(Connection con) {
try {
if (con != null && !con.isClosed()) {
System.out.println("con is not null");
con.close();
}
if (con == null) {
System.out.println("con = null");
}
if (con.isClosed()) {
System.out.println("con is closed");
}
} catch (SQLException e) {
e.printStackTrace();
} finally {
con = null;
System.out.println("con = " + con + " after finally");
}
}
}
运行结果如下:
i = 0con is not null
con is closed
con = null after finally
con1 = com.mchange.v2.c3p0.impl.NewProxyConnection@4d6c6310
con1 is closed
i = 1
con is closed
con = null after finally
con1 = com.mchange.v2.c3p0.impl.NewProxyConnection@4d6c6310
con1 is closed
i = 2
con is closed
con = null after finally
con1 = com.mchange.v2.c3p0.impl.NewProxyConnection@4d6c6310
con1 is closed
i = 3
con is closed
con = null after finally
con1 = com.mchange.v2.c3p0.impl.NewProxyConnection@4d6c6310
con1 is closed
i = 4
con is closed
con = null after finally
con1 = com.mchange.v2.c3p0.impl.NewProxyConnection@4d6c6310
con1 is closed
可看出,每次虽然在testClose()的finally中con=null,但回到main之后,con仍然不是null。由此可见上述1.2.这两点都不能成为在finally中写上con=null的理由。但第3点,出于多线程考虑,希望了解的大牛帮忙解答以下~
最后,如果实在想在关闭连接的时候,把连接置为null,那可以考虑重写close()方法(不推荐)。