[Geoserver-devel] [JIRA] (GEOS-10490) Could layer within GeoServer config, GWC out of synch

_Failed_to_Retrieve · May 13, 2022, 10:04pm

Jody Garnett created an issue

Could layer within GeoServer config, GWC out of synch

Issue Type:	Task
Affects Versions:	2.21-RC
Assignee:	Unassigned
Components:	GWC
Created:	14/May/22 12:04 AM
Environment:	Unbuntu
Priority:	Low
Reporter:	Jody Garnett

This error message is a side-effect of a catalogue failure that happens after the fact. The complete error message is:

13 038 10:38:20 ERROR  [geowebcache.GeoWebCacheDispatcher] - Request failed
java.lang.IllegalStateException: Could not locate a layer or layer group with id LayerInfoImpl-4a15a5e5:17e9b318d34:-7fde within GeoServer configuration, the GWC configuration seems to be out of synch
        at org.geoserver.gwc.layer.GeoServerTileLayer.getPublishedInfo(GeoServerTileLayer.java:364)
        at org.geoserver.gwc.layer.GeoServerTileLayer.isEnabled(GeoServerTileLayer.java:322)

And the “problem” shows up when this attempt to get published info is called:

Listing all layers
- Wicket: GWCIconFactory.getSpecificLayerIcon(GWCIconFactory.java:58)
- https://osgeo-org.atlassian.net/browse/GEOS-7634
- https://osgeo-org.atlassian.net/browse/GEOS-7202
- https://osgeo-org.atlassian.net/browse/GEOS-7633
- https://osgeo-org.atlassian.net/browse/GEOS-7892
- https://osgeo-org.atlassian.net/browse/GEOS-8281
WMTS GetCapabilities
- WMTSGetCapabilities.contents(WMTSGetCapabilities.java:435)

As the above bug reports show we expect GeoServer and GWC have gotten our of sync during a delete or move between workspaces.

This mitigation task is but to prevent GeoServerTileLayer.getPublishedInfo() returning null from causing problems:

Log a warning mentioning the GeoServerTileLayer name, and information on what specific gwc-layers/LayerInfo.xml or LayerGroupInfoIml file is troubled.
Treat out of sync GeoServerTileLayer as disabled so that WMTS GetCapabilities and Wicket can continue to function (while sending warnings to log)
Propose making a tool to re-sync (or at least clean up the mess) similar to disabling and enabling tile caching for the affected layer
If this really occurs when a layer is deleted then we are likely finding an orphaned GeoServerTileLayer (which can be removed)

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198-sha1:8950bff)