Re: Should application do connection.close()? -- JAVA400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Should application do connection.close()?
From: Thorbjoern Ravn Andersen <ravn@xxxxxxxxxx>
Date: Fri, 20 Mar 2009 20:27:33 +0100
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Lim Hock-Chai skrev:

Once again I'm a newbie.
Looking at our code, I see that some of the methods of some classes are
using the AS400JDBCConnectionPool.getConnection() method to get a
java.sql.Connection object. Once the connection object is obtained,
should this same method call the connection.close() once it is finished

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.

Follow-Ups:

Re: Should application do connection.close()? , David Gibbs

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.