Is connection.close() sufficient?

[Gaurav Jain]

Calling connection.close in the finally block ensures that the connection is released ir still a reference is present to that connection and some additional measures need to be taken to release the connection?

Is it safe to do our own connection pooling or let the WAS connection pool handle it?

[Jeanne Boyarsky]

Gaurav,
If you are using a connection pool, close() returns the connection to the pool rather than actually closing it. This is the desired behavior.

If at all possible, you should let WAS handle connection pooling. In other words, you need a really good reason not to.

[Guy Allard]

Gaurav - You should be working with some kind of "framework" that supports connection poooling.

Pardons to Jeanne, but that does not necessarily mean WAS.

Guy

[Annie Smith]

Some of the DB drivers require explicit closing of the ResultSet and Statments too. Some manage it on the clsoing of Connection. But generally, it is better to close ResultSet, Statement and Connection explicitly.
[ March 24, 2005: Message edited by: Annie Smith ]

[Jeanne Boyarsky]

Guy,
I only mentioned WAS because that's what Gaurav said he was using. While you could use a different connection pool, I would use the one provided by the app server.