Hi,
We are in the process of upgrading from geoserver 1.5 to 1.6.2. We are
having issues with some connections being leaked in 1.5.
I read that there is some connection pooling support in 1.6.2, but what I am
really looking for is the possibility to use a database connection pool,
which is managed by the container (in our case Tomcat), so I could manage
those pools using the container?
Did anybody successfully do this?
Thanks
Thomas
--
View this message in context: http://www.nabble.com/Database-connection-pooling-or-using-JNDI-datasources-in-Geoserver-1.6.2-tp16736466p16736466.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
thomas_abc ha scritto:
Hi,
We are in the process of upgrading from geoserver 1.5 to 1.6.2. We are
having issues with some connections being leaked in 1.5.
I read that there is some connection pooling support in 1.6.2, but what I am
really looking for is the possibility to use a database connection pool,
which is managed by the container (in our case Tomcat), so I could manage
those pools using the container?
Did anybody successfully do this?
There is no support for JNDI based connection pools in GeoServer.
The underlaying code is able to, but we lack a UI for it.
It's really just a matter of creating a new datastore factory class that
asks for a connection pool name instead of the pool configuration parameters, but none of the developers has had such a need so far.
I have opened a jira issue about this some time ago:
http://jira.codehaus.org/browse/GEOS-1324
but other stuff is simply getting more priority. Patches welcomed (if
you can develop just ask for directions, we'll assist you in setting
up the dev env)
Cheers
Andrea