aspose file tools*
The moose likes JDBC and the fly likes closing the database connection Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "closing the database connection" Watch "closing the database connection" New topic
Author

closing the database connection

trupti nigam
Ranch Hand

Joined: Jun 21, 2001
Posts: 613
Hello All,

In my code, I have made sure that I am closing all the open dataBase connections like below:

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

where conn is the connection object. and null is for preparedStatement.

In the dao close() method if connection is not null, con.close() (java method) is called.
While debugging the application , I found out that the connection is not getting close.

my question is : does the connection is closed by calling connection.close method (provied by jdk) or it just marks it for garbage collection.

How can I make sure that the connection is getting closed? (is it by passing exclusively null for connection object?)

Thanks,
Trupti
[ April 19, 2005: Message edited by: trupti nigam ]
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 31057
    
232

Trupti,
If you are using a connection pool, close() returns the connection to the pool. If you are not using a connection pool, close() closes the connection.

close() does not null out the reference to the connection object in your code. If you try to use the connection, you will get a StaleConnectionException. However, having this reference does not affect the connection resources.

Why aren't you closing the PreparedStatement too?


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
 
Consider Paul's rocket mass heater.
 
subject: closing the database connection