Is there any chance of geowebacache change causing this? I did add a servlet listener to gwc startup to configure logging, but I did not think that would be used when geowebcache is embeded. -- Jody Garnett
On Apr 15, 2022 at 8:13:37 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi, > the REST API does not seem to be working anymore on the main branch, > I get the same exception both locally and on other demo servers (using > Tomcat and the latest GeoServer nightly build): > > javax.servlet.ServletException: Circular view path [rest]: would dispatch > back to the current handler URL [/geoserver/rest] again. Check your > ViewResolver setup! (Hint: This may be the result of an unspecified view, due > to default view name generation.) > at > org.springframework.web.servlet.view.InternalResourceView.prepareForRendering(InternalResourceView.java:210) > at > org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:148) > at > org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:316) > at > org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1376) > at > org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1121) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1060) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1459) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799) > at > org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1631) > > > And here is the equivalent trace from a Tomcat deploy: > > javax.servlet.ServletException: Circular view path [rest]: would dispatch > back to the current handler URL [/geoserver/rest] again. Check your > ViewResolver setup! (Hint: This may be the result of an unspecified view, due > to default view name generation.) > > org.springframework.web.servlet.view.InternalResourceView.prepareForRendering(InternalResourceView.java:210) > > org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:148) > > org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:316) > > org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1376) > > org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1121) > > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1060) > > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) > > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) > > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) > javax.servlet.http.HttpServlet.service(HttpServlet.java:655) > > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) > javax.servlet.http.HttpServlet.service(HttpServlet.java:764) > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) > > org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:28) > > org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:73) > > So it does not seem container dependent... > At first I thought, this may be the Spring upgrade... but turns out, the > REST API is working > fine on 2.20.x (again, Tomcat + latest build). > > I quickly looked through the latest commits but I don't see anything > obvious that might cause this behavior... and yet, what caused it should be > pretty recent, I was using the REST API on main, without issues, one or two > days ago.... > > Is the above error ringing any bell to anyone? > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 333 8128928 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
