If your datasource is in Tomcat GlobalNamingContext, Tomcat will take care
of it. If it is in your context, you will have to destroy it in a servlet
destroy method.
-Original Message-
From: Lucie Chan [mailto:[EMAIL PROTECTED]
Sent: January 7, 2005 11:40 PM
To:
Are you using a global pool or is the pool just for that app?
If global, this will kill the connections for all the apps. Not something
you want to do in production but will be fine in development.
So remember to remove this before going live, if global.
That is what I get for reading while
parameter
nameremoveAbandoned/name
valuetrue/value
/parameter
parameter
nameremoveAbandonedTimeout/name
value60/value
/parameter
Time in seconds.
You need to release connections when you are done with them, con.close() ;
This is similar to using a direct connection to the jdbc except this
time the only difference is where you got the connection object from.
Calling con.close() ;
will release the driver back to the connection pool.
Lucie
In your servlet's destroy() method (I am using Struts
and plugins, and use the plugin's destroy() method),
add the following code:
((BasicDataSource) ds).close();
That is assuming your data source is named 'ds'. This
will close all connections.
Dustin
--- Lucie Chan [EMAIL PROTECTED] wrote:
