Re: Should application do connection.close()?

When the method does AS400JDBCConnectionPool.getConnection(), it will
return a java.sqlConnection object to the caller. I'm assuming that the
close() method of this returned Connection object is being overriden to
not close the connection. Instead, it put it back to the pool. That is
just my guess. The doc does really say anyhting about this. Can anyone
confirm?

"David Gibbs" <david@xxxxxxxxxxxx> wrote in message
news:<mailman.11131.1237577671.26163.java400-l@xxxxxxxxxxxx>...

Thorbjoern Ravn Andersen wrote:

If I recall correctly the AS400JDBCConnectionPool does not use

close()

to release the connection and put it back in the pool. Read the

docs

very carefully with regard to the IBM Java Toolbox - many things are

different than elsewhere, most likely due to it being designed a

long

time ago before de-facto standards arose.

Yeah, I was wondering about that myself ... I poked in the code a bit

and didn't find anything that explicitly returned the connection to the
pool ... but there seems to be a few events that are managed that might
still do that.

None the less, the answer to Lim's question is still yes, you should

close the connection when you are done with it. And don't depend on
garbage collection to do anything for you.

david

--
IBM i on Power - For when you can't afford to be out of business