I've recently been contacted by my company's database team, saying that my SmartGWT app is holding 200+ connections to one of our prod databases, effectively locking everybody else out. Looking through the SmartGWT Datasource samples, I see no mention of closing connections whatsoever, and I was under the impression that this was all taken care of under the hood. I bounced the server to free up the connections but am facing the same problem, less than a week later.
The application uses Datasource connections on both the client and server side (com.smartgwt.client.data.DataSource and com.isomorphic.datasource.DataSource), and they are instantiated with DataSource.get("widgetsDS") and DataSourceManager.getDataSource("linksDS"), respectively.
Is there something major (regarding connection pooling, closing connections, etc) that I'm missing?
Here is the relevent parts of the application configuration:
Thanks!
SmartGWT Power (4.0.d20130618)
SmartClient Version: v9.0d_2013-06-18/PowerEdition Deployment (built 2013-06-18)
The application uses Datasource connections on both the client and server side (com.smartgwt.client.data.DataSource and com.isomorphic.datasource.DataSource), and they are instantiated with DataSource.get("widgetsDS") and DataSourceManager.getDataSource("linksDS"), respectively.
Is there something major (regarding connection pooling, closing connections, etc) that I'm missing?
Here is the relevent parts of the application configuration:
Code:
########################
# SmartGWT Server
webRoot: __AUTODETECT__
isomorphicPathRootRelative: workbench/sc
sql.defaultDatabase: PostgreSQL
sql.PostgreSQL.driver.serverName: dtord01qdb01d
sql.PostgreSQL.driver.portNumber: 5432
sql.PostgreSQL.driver.databaseName: prod_db
sql.PostgreSQL.driver.user: produser
sql.PostgreSQL.driver.password: password
project.datasources: $webRoot/ds
RPCManager.enabledBuiltinMethods: *SmartGWT Power (4.0.d20130618)
SmartClient Version: v9.0d_2013-06-18/PowerEdition Deployment (built 2013-06-18)