Thanks Jody, I'm asking internally details to reproduce, hopefully I'll come back to you with some more information on this issue. Best, C.
Il giorno mar 27 lug 2021 alle ore 18:28 Jody Garnett < [email protected]> ha scritto: > Checking Jira this issue has not been reported yet, it would be good to > step through this in a debugger to see what what is going wrong. > > It looks like the code is having a a bad time with lots of warnings before > the failure with SecuredLayerInfo[LayerInfoImpl[test, > resource:FeatureTypeInfoImpl[test]]]. > > Can you have a look at the workspace that was created prior to deleting? > Or attach the the workspace folder (as long as it does not contain customer > sensitive information) when creating a Jira ticket. > -- > Jody Garnett > > > On Thu, 22 Jul 2021 at 01:53, carlo cancellieri < > [email protected]> wrote: > >> 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. >> >> >> -- >> Mr. Carlo Cancellieri >> *skype*: ccancellieri >> *Twitter*: @cancellieric >> *LinkedIn*: http://it.linkedin.com/in/ccancellieri/ >> _______________________________________________ >> Geoserver-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > -- > -- > Jody Garnett > -- Mr. Carlo Cancellieri *skype*: ccancellieri *Twitter*: @cancellieric *LinkedIn*: http://it.linkedin.com/in/ccancellieri/
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
