Too many open connections from Tomcat to MySQL?

Question

<?xml version='1.0' encoding='utf-8'?>
<Context>
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<Resource
name="jdbc/RealmDB" auth="Container" type="javax.sql.DataSource"
username="root" password="password" driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/monk"
maxActive="-1" maxIdle="5" maxWait="5000"
removeAbandoned="true" removeAbandonedTimeout="60"
testWhileIdle="true" timeBetweenEvictionRunsMillis="180000"/>
<Realm
className="org.apache.catalina.realm.DataSourceRealm"
dataSourceName="jdbc/RealmDB" localDataSource="true"
digest="MD5"
userTable="user" userNameCol="user_name" userCredCol="password"
userRoleTable="tcrole" roleNameCol="role_name" />
</Context>
Is there a way in here to auto close inactive connections after say 10 seconds? Is that the removeAbandonedTimeout or the Eviction section? Would this be better off posted on the tomcat user listing?
Edited by: TheWhiteKnight on Oct 29, 2009 8:00 PM

Answer 1

Actually BalusC, I like this. This seems to define the entire cycle quite nicely and CLEAN. This will be very helpful when phase II rolls out. Right now I need to just patch the thing and get it running "well".
I've also had to implement some new methods to clean up some of the junk that is left open. I have found RS's that are closed, but no corresponding connection / statement's are being closed. So when I have a return statement like:
return ConnectionPool.getConnection().createStatement().executeQuery(sqlStatement);
{code]
that is called from the presentation layer, logically (to me) the only place to close the connection / statement associated with that RS is in the presentation layer.  As of right now.  This will change on phase II.  If I am wrong please correct me in this.
Something that is happening now though since I have started explicitly closing the connections and statements.  It seems that my ConnectionPool is running out of connections. I can increase the size of the pool, but it worked just fine before with the amount of connections I have set.  When I call .close() on the connection, does that "recycle" the connection back to the pool?  I know there has to be resources bleeding someplace, however, this has only started happening (more often) since I have been closing things where I find them.
Any ideas on this?
Also will converting the basic generic queries to stored procedures help in the performance?  I know that I'll still have to have a connection, but if I can have less java coded sql statements and more SP's would that help in efficiency between MySQL and Tomcat?