| With some simple kml network links using http://<host>/geoserver/wms/kml?layers=mylayer and with KML settings such that the generated network link is: /geoserver/wms?service=wms&request=GetMap&version=1.1.1&format=application/vnd.google-earth.kml+xml&layers=mylayer&styles=mystyle&height=2048&width=2048&transparent=false&srs=EPSG:4326&format_options=AUTOFIT:true;KMATTR:true;KMPLACEMARK:false;KMSCORE:58;MODE:refresh;SUPEROVERLAY:false&BBOX=-87.12804508712404,27.16327139811996,-69.86870464467852,36.76450394960558 It takes several minutes to complete (even with WMS max rendering time set to 60s). mylayer in this scenario is OSM points so > 3.3B points. Looking in pg_stat_activity I can see a query running on osm_point getting all geometries, without a where clause. I produced an error in the GeoServer log by killing it with pg_terminate_backend: java.io.IOException: Error occured calculating bounds for osm_point
at org.geotools.jdbc.JDBCDataStore.getBounds(JDBCDataStore.java:1350)
at org.geotools.jdbc.JDBCFeatureSource.getBoundsInternal(JDBCFeatureSource.java:534) This issue appears to be new at approx 2.11. These same network links used to work fine (maybe at 2.10 or 2.9). |
