On Wed, Jun 26, 2013 at 10:45 AM, David Niedzielski <
david.niedziel...@gmail.com> wrote:
> Thanks for the reply. In our case, sadly, we have separate databases. One
> for each data store. The timeouts to which you allude seems to be key,
> because they obviously do not abide by the connection tim
Thanks for the reply. In our case, sadly, we have separate databases. One
for each data store. The timeouts to which you allude seems to be key,
because they obviously do not abide by the connection timeout associated
with the stores. Indeed, these single connections are up for as long as
geoserver
On Wed, Jun 26, 2013 at 4:46 AM, David Niedzielski <
david.niedziel...@gmail.com> wrote:
> Using GeoServer 2.2.1 and 2.3 with a large number of PostGIS-backed
> datastores under TomCat 6.2.These stores are rarely used, so we'd like
> them to not tie up a PostgreSQL connection until one is actu
Using GeoServer 2.2.1 and 2.3 with a large number of PostGIS-backed
datastores under TomCat 6.2.These stores are rarely used, so we'd like
them to not tie up a PostgreSQL connection until one is actually needed.
Thus, we set min_connections=0 in the datastore.xml associated with each
store. In