We also have more questions: 1. We have been using the same settings (ie, max connections = 10) with Geoserver 2.0.2. We have used that for several years and never had this problem. This problem started happening when we switched to Geoserver 2.6.2. Just wondering if this is caused by some change in the Geoserver code (for example, it needs to hit the database more frequently...)?
2. Sometimes we would observe that the map really lags as we navigate around (we have a Postgres database that stores our map data, and we connect a datastore in Geoserver to point to the Postgres database. Then we add new layers to Geoserver by choosing from the postgres datastore, and finally we add these layers to a layergroup that our application can access via WMS). Is the lagging caused by waiting for a connection from the connection pool, and if it still doesn't get a connection after it reaches the 'time out' value, it will give the "Cannot get a connection, pool error Timeout waiting for idle object " error? Thank you very much, appreciate your reply in advance! E -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-rendering-failed-on-connection-pool-error-tp5104815p5216771.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
