Good morning guys,
a user has reported an issue over geoserver-2.17.2.
The issue should be reproducible performing a DELETE over a workspace recursively (wwweek is the workspace):
https://MY_GEOSERVER/rest/workspaces/wwweek?recurse=true
But it could be related to a specific layer configuration.
The user is using geocat bridge and he is unable to UPDATE an existing project.
Geo Cat bridge, during the update, deletes cascading (via REST) the workspace to recreate it again.
It’s interesting to note that restarting geoserver the issue is ‘resolved’ so the user can update (deleting everything and recreating) the workspace via geocatbridge.
But after the first update the issue pops up again.
The reported error is a 500 coming from a proxy class resolution failure (please check the attached log file)
I’ve also looked around for existing bugs with no luck (there are some similar already solved but quite old: geoserver 2.10)
My questions:
is this something familiar/known?
do I need to create a bug about this? or it’s something already resolved? (I’m over 2.17.2 and it’s production, and we are not owning the data so we can’t easily try with a newer release.
Best,
C.
(attachments)
geoserver_edit_22072021.log (18.2 KB)
···
Mr. Carlo Cancellieri
skype: ccancellieri
Twitter: @cancellieric
LinkedIn: http://it.linkedin.com/in/ccancellieri/