databaseContext.xml currently uses org.springframework.jdbc.datasource.DriverManagerDataSource for DB connections. This is not a DB connection pool. It gets a new DB connection on each request. This is a problem because
1. It is inefficient 2. If there is an error, the Calendar can continue obtaining new DB connections without bound until the DB server runs out of connections
Change to use Apache DB Commons or c3p0 connection pool. Announcements uses the former. Simple Content Portlet uses the latter.
Critical
databaseContext.xml currently uses org.springframework.jdbc.datasource.DriverManagerDataSource for DB connections. This is not a DB connection pool. It gets a new DB connection on each request. This is a problem because
1. It is inefficient
2. If there is an error, the Calendar can continue obtaining new DB connections without bound until the DB server runs out of connections
Change to use Apache DB Commons or c3p0 connection pool. Announcements uses the former. Simple Content Portlet uses the latter.