Calling close() on a pooled connection simply returns it to the pool, however, i have seen some cases where calling ti twice closes it for real. Don't do that.
If you are interested in other options that eliminate that concern, you may want to try iBATIS - you would still use SQL, but it manages the connections, statements, resultsets, etc, and maps the results of the SQL to objects. Larry On 4/5/06, Abh N <[EMAIL PROTECTED]> wrote: > Hi, > > we are implementing the connection pooling in our application. > > connections are taken from the data source. > > After getting the connection i need to confirm whether i have to explictly > close the connection > like conn.close () > > i want to know in above case whether connection will be release to the pool > or will get closed. > > i have a doubt as in above case the connection might be getting closed and > might not be available for re-use. > > > > > --------------------------------- > Jiyo cricket on Yahoo! India cricket > Yahoo! Messenger Mobile Stay in touch with your buddies all the time. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
