Hi,
using GeoServer 3 (and also the release candidate before) I have the problem that seeding for a single layer is permanently broken after the cascaded backend service returned errors. When all seeding tasks have crashed because of this, I’m unable to restart seeding for this layer
unless I’m restarting the GeoServer service. Seeding of other layers is not affected by this.
Here is an excerpt from the logs:
Backend service temporarily fails:
02:00:03 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Error rendering coverage on the fast path
Caused by: org.geoserver.platform.ServiceException: java.io.IOException: Server returned HTTP error code 503 for URL https://my.host/wms?REQUEST=GetMap&FORMAT=image/png&CRS=EPSG:31252&BBOX=298474.18043081183,-16301.855093511598,298535.87729143444,-16239.971868633553&VERSION=1.3.0&STYLES=&SERVICE=WMS&WIDTH=4921&HEIGHT=4906&TRANSPARENT=TRUE&LAYERS=Topographie-GISWMS-Web
02:00:03 ERROR [seed.MTSeeder] - Problem communicating with GeoServer
org.geowebcache.GeoWebCacheException: Problem communicating with GeoServer
Caused by: java.lang.IllegalStateException: Expected: RenderedImageMap, got null
After this happend for all seeding tasks, seeding finishes:
02:03:14 INFO [seed.GWCTask] - Thread group finished SEED task after 307.741 seconds
When the backend service is up again, restarting seeding immediately leads to the following errors:
02:16:03 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: Error rendering coverage on the fast path
Caused by: org.geoserver.platform.ServiceException: org.apache.hc.core5.http.ConnectionRequestTimeoutException: Timeout deadline: 180000 MILLISECONDS, actual: 180012 MILLISECONDS
Interestingly, I’ve set all timeouts I could find to 240s, so I’m wondering where this 180s timeouts come from. And looking at older GeoServer logs I wasn’t able to find similar entries for 2.x versions of GeoServer.
Any ideas?
Regards
Daniel