For standalone applications, you probably should not use a Connection Pool. In other words, you should either pass in your own connection, or use a non-pooling datasource implementation. I think you can achieve this effect by setting the max idle connections on SimpleDataSource to 0, or you can just implement your own datasource and plug it into iBATIS. The other way you could deal with it would be to cast the DataSource to SimpleDataSource and call .forceCloseAll().
Cheers, Clinton On Tue, Jun 2, 2009 at 9:59 PM, Nathan Modrzewski <nmodrzew...@eaglexm.com>wrote: > I will look at doing that. Thanks for the info. > > > > n Nathan > > > > *From:* Nicholoz Koka Kiknadze [mailto:kikna...@gmail.com] > *Sent:* Tuesday, June 02, 2009 3:02 PM > *To:* user-java@ibatis.apache.org > *Subject:* Re: FW: Connection Closing Problem > > > > I think what happens to open (pooled) connection upon JVM exit depends on > JDBC driver. > > > IMO if you were using SimpleDataSource of iBatis, you'd have to call > forceCloseAll() to close all pooled connections at the end of execution of > your app (I think I have even used that years ago). Not sure about DBCP, > but I bet calling basicDataSource.close() must help. > > GL > > On Wed, Jun 3, 2009 at 12:18 AM, Nathan Modrzewski < > nmodrzew...@eaglexm.com> wrote: > > Not yet…getting ready too. > > > > If I’m using Apache Dbcp to handle connection pooling, do I have to > manually close the pooling objects? > > > > > > >
