Hi I'm also encountering this problem occasionally, but I only set 'Max Connections' to 10 (so I don't think it's exceeding the 100 connections that postgres allows by default). I have only configured one datastore, and traffic is not heavy. Most of the time things are working fine, but occasionally I get exactly the same stack trace. The map would start to lag, and then the "Unable to obtain connection: Cannot get a connection, pool error Timeout waiting for idle object " error would appear.
Just to see what might happen, I tried reducing 'Max Connections' to 1, but things were working fine. I couldn't find a pattern of when this problem occurs. What I'm using: GeoServer-2.6.2 Tomcat 7 PostgreSQL 8.4 I'm wondering if anyone has ideas on what might cause this problem? Some people suggested configuring a JNDI Connection Pool with Tomcat instead of using Apache Commons connection pool, and setting 'maxActive' to -1. https://cgsrv1.arrc.csiro.au/blog/2011/05/26/troubleshooting-guide-for-common-geoserver-problems-during-deployment/ http://comments.gmane.org/gmane.comp.gis.geoserver.user/40336 Would you recommend to try this approach too? Thanks E -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-rendering-failed-on-connection-pool-error-tp5104815p5216611.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
