[Geoserver-devel] [JIRA] (GEOS-8181) KML reflector attempts to query all records in table

GeoServer GeoServer Developer
1

Jason Newmoyer created an issue

GeoServer / BugGEOS-8181

KML reflector attempts to query all records in table

Issue Type:

BugBug

Affects Versions:

2.11.1

Assignee:

Unassigned

Components:

Google Earth KML Output

Created:

12/Jun/17 5:28 PM

Priority:

MediumMedium

Reporter:

Jason Newmoyer

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).

Add Comment

Add Comment

This message was sent by Atlassian JIRA (v1000.1043.2#100046-sha1:a1d8ef5)

Atlassian logo