Hello Isomorphic,
SmartGWT 3.1p v8.3p_2013-04-01/PowerEdition Deployment, Tomcat 7, Oracle 10, FireFox 10
Is there any plan for you guys to upgrade from Apache DBCP 1.2.2, that you have in your package? Also is there any plan to allow another pooling mechanism such as the new Tomcat JDBC Pool (http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html)?
My team is having problems with performance (query speed) once connections in the pool have been up for a couple days. We have tried to use the information here http://www.smartclient.com/smartgwtee-latest/javadoc/com/smartgwt/client/docs/SqlConnectionPooling.html and have tried tweaking
While these settings do what they are supposed to do, they are not solving our problem. The new feature "maxAge" in the Tomcat JDBC Pool seems like it would be perfect to solve the issue we are having. It seems our only other option would be to have a batch job running in Oracle that will kill connections after a certain amount of time. Have any of your other customers been having similar issues, or do have any other insights?
Thanks.
SmartGWT 3.1p v8.3p_2013-04-01/PowerEdition Deployment, Tomcat 7, Oracle 10, FireFox 10
Is there any plan for you guys to upgrade from Apache DBCP 1.2.2, that you have in your package? Also is there any plan to allow another pooling mechanism such as the new Tomcat JDBC Pool (http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html)?
My team is having problems with performance (query speed) once connections in the pool have been up for a couple days. We have tried to use the information here http://www.smartclient.com/smartgwtee-latest/javadoc/com/smartgwt/client/docs/SqlConnectionPooling.html and have tried tweaking
Code:
testWhileIdle, timeBetweenEvictionRunsMillis, minEvictableIdleTimeMillis, numTestsPerEvictionRunThanks.