Re: [Geoserver-users] WMS GetCapabilities Java translator error
Hi, please see my answers bellow: > I always thought all the information needed for the GetCapabilities > response is already stored in the Workspace as XML files and processing > a number of XML files to create the GetCapabilites response is what > GoeServer does to create the response. This is *almost* the expected behavior, GeoServer will try to cache meta-data as much as possible, but after each restart the first time a layer is used GeoServer may ping the data source to obtain or validate the meta-data. Without more details is hard to know what's exactly happening in this case. Kind regards, Nuno Oliveira On Mon, 2020-02-03 at 17:58 -0500, Nedim Oren wrote: > just to understand the process...> Is GeoServer going trough all of the > individual data sources, making connection to each one of them one by one to > verify/gather information for GetCapabilities response? I always thought > all the information needed for the GetCapabilities response is already stored > in the Workspace as XML files and processing a number of XML files to create > the GetCapabilites response is what GoeServer does to create the response.> > On Mon, Feb 3, 2020 at 11:22 AM Nuno Oliveira > wrote:> > Hi, > > just had a quick look at the log, the capabilities generation fails because > > GeoServer fails to obtain the feature type for layer trecho_drenagem_1: > > > > 2020-01-07 09:23:45,892 ERROR [geoserver.wms] - An error occurred > > > > trying to determine if the layer is geometryless > > java.io.IOException: Schema 'trecho_drenagem_1' does not exist. > > > > What's not clear to me is why GeoServer ends up on that state, querying > > > > a layer that apparently doesn't exists. > > > > Hope it helps, > > Nuno Oliveira > > > > On Mon, 2020-01-13 at 09:35 -0300, Coordenador GEOBASES wrote: > > > Hey there ! > > > I have a GeoServer running along to GeoNode and when I call WMS service > > > with GetMap and GetFeature requests it works, but when I make a request > > > for GetCapabilities it returns a java translator error. > > > Would somebody help me please?> > > > > > > > > The issue log in attach. > > > > > > Thanks > > > > > > > > > > > > > > > Giuliano Grigolin > > > Coordenador Técnico > > > 27-3636.8081 > > > coordena...@geobases.es.gov.br > > > Av. Marechal Mascarenhas de Moraes, 2.524 > > > Jesus de Nazareth, Vitória - ES > > > CEP: 29052-015 > > > > > > > > > Antes de imprimir pense em seu compromisso com o meio ambiente. > > > As > > > informações existentes nesta mensagem e em seus arquivos anexados são > > > para uso restrito, sendo seu sigilo protegido por lei. Caso você não > > > seja o destinatário, saiba que leitura, divulgação ou cópia são > > > proibidas. Neste caso, favor notificar o remetente e apagar as > > > informações. O uso impróprio destas informações será tratado conforme as > > > normas da empresa e a legislação em vigor. > > > ___ > > > Geoserver-users mailing list > > > > > > Please make sure you read the following two resources before posting to > > > this list: > > > - Earning your support instead of buying it, but Ian Turton: > > > http://www.ianturton.com/talks/foss4g.html#/ > > > > > > - The GeoServer user list posting guidelines: > > > http://geoserver.org/comm/userlist-guidelines.html > > > > > > > > > If you want to request a feature or an improvement, also see this: > > > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > > > > > > > > > > Geoserver-users@lists.sourceforge.net> > > https://lists.sourceforge.net/lists/listinfo/geoserver-users> > > > > -- > > Regards, > > Nuno Oliveira > > == > > GeoServer Professional Services from the > > experts! > > Visit http://goo.gl/it488V for more information. > > for more information. > > == > > > > Nuno Miguel Carvalho Oliveira > > @nmcoliveira > > Software Engineer > > > > GeoSolutions S.A.S. > > Via di Montramito 3/A > > 55054 Massarosa (LU) > > Italy > > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > > > http://www.geo-solutions.it> > 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 >
Re: [Geoserver-users] WMS GetCapabilities Java translator error
On Tue, Feb 4, 2020 at 12:08 AM Nedim Oren wrote: > just to understand the process... > Is GeoServer going trough all of the individual data sources, making > connection to each one of them one by one to verify/gather information for > GetCapabilities response? I always thought all the information needed for > the GetCapabilities response is already stored in the Workspace as XML > files and processing a number of XML files to create the GetCapabilites > response is what GoeServer does to create the response. > Not all the information is stored, the list of attributes is computed at runtime, but it's stored in a cache in the ResourcePool. The cache by default has 100 hard references plus a free amount of soft references that can be freed when there is GC pressure. The number of hard references is tunable, see https://docs.geoserver.org/stable/en/user/configuration/globalsettings.html#feature-type-cache-size The capabilities transformer needs to perform some checks, so it iterates over all the feature types, the first time actually opening connections, the other times (hopefully) hitting the cache. Mind, calls to "reset" and "reload" (status page, REST API) wipe out the cache completely. Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 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-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] WMS GetCapabilities Java translator error
just to understand the process... Is GeoServer going trough all of the individual data sources, making connection to each one of them one by one to verify/gather information for GetCapabilities response? I always thought all the information needed for the GetCapabilities response is already stored in the Workspace as XML files and processing a number of XML files to create the GetCapabilites response is what GoeServer does to create the response. On Mon, Feb 3, 2020 at 11:22 AM Nuno Oliveira < nuno.olive...@geo-solutions.it> wrote: > Hi, > just had a quick look at the log, the capabilities generation fails > because GeoServer fails to obtain the feature type for layer > *trecho_drenagem_1*: > > 2020-01-07 09:23:45,892 ERROR [geoserver.wms] - An error occurred trying > to determine if the layer is geometryless > java.io.IOException: Schema 'trecho_drenagem_1' does not exist. > > What's not clear to me is why GeoServer ends up on that state, querying a > layer that apparently doesn't exists. > > Hope it helps, > Nuno Oliveira > > On Mon, 2020-01-13 at 09:35 -0300, Coordenador GEOBASES wrote: > > Hey there ! > I have a GeoServer running along to GeoNode and when I call WMS service > with GetMap and GetFeature requests it works, but when I make a request for > GetCapabilities it returns a java translator error. > Would somebody help me please? > > The issue log in attach. > > Thanks > > > > > > Giuliano Grigolin > Coordenador Técnico > 27-3636.8081 > coordena...@geobases.es.gov.br > Av. Marechal Mascarenhas de Moraes, 2.524 > Jesus de Nazareth, Vitória - ES > CEP: 29052-015 > > > > -- > > *Antes de imprimir pense em seu compromisso com o meio ambiente.* > As informações existentes nesta mensagem e em seus arquivos anexados são > para uso restrito, sendo seu sigilo protegido por lei. Caso você não seja o > destinatário, saiba que leitura, divulgação ou cópia são proibidas. Neste > caso, favor notificar o remetente e apagar as informações. O uso impróprio > destas informações será tratado conforme as normas da empresa e a > legislação em vigor. > > ___ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to this > list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > Geoserver-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-users > > -- > Regards, > Nuno Oliveira > == > GeoServer Professional Services from the > experts! > Visit http://goo.gl/it488V for more information. > == > > Nuno Miguel Carvalho Oliveira > @nmcoliveira > Software Engineer > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > http://www.geo-solutions.ithttp://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-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > _
Re: [Geoserver-users] WMS GetCapabilities Java translator error
Hi, just had a quick look at the log, the capabilities generation fails because GeoServer fails to obtain the feature type for layer trecho_dre nagem_1: 2020-01-07 09:23:45,892 ERROR [geoserver.wms] - An error occurred trying to determine if the layer is geometryless java.io.IOException: Schema 'trecho_drenagem_1' does not exist. What's not clear to me is why GeoServer ends up on that state, querying a layer that apparently doesn't exists. Hope it helps, Nuno Oliveira On Mon, 2020-01-13 at 09:35 -0300, Coordenador GEOBASES wrote: > Hey there ! > I have a GeoServer running along to GeoNode and when I call WMS > service with GetMap and GetFeature requests it works, but when I make > a request for GetCapabilities it returns a java translator error. > Would somebody help me please? > > The issue log in attach. > > Thanks > > > > > > Giuliano Grigolin > Coordenador Técnico > 27-3636.8081 > coordena...@geobases.es.gov.br > Av. Marechal Mascarenhas de Moraes, 2.524 > Jesus de Nazareth, Vitória - ES > CEP: 29052-015 > > > > Antes de imprimir pense em seu compromisso com o meio ambiente. > As informações existentes nesta mensagem e em seus arquivos anexados > são para uso restrito, sendo seu sigilo protegido por lei. Caso você > não seja o destinatário, saiba que leitura, divulgação ou cópia são > proibidas. Neste caso, favor notificar o remetente e apagar as > informações. O uso impróprio destas informações será tratado conforme > as normas da empresa e a legislação em vigor. > ___ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting > to this list: > - Earning your support instead of buying it, but Ian Turton: http://w > ww.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: http://geoserver.org/co > mm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: ht > tps://github.com/geoserver/geoserver/wiki/Successfully-requesting- > and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Regards, Nuno Oliveira == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it 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-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] WMS GetCapabilities Java translator error
Hey there ! I have a GeoServer running along to GeoNode and when I call WMS service with GetMap and GetFeature requests it works, but when I make a request for GetCapabilities it returns a java translator error. Would somebody help me please? The issue log in attach. Thanks Giuliano Grigolin Coordenador Técnico 27-3636.8081 coordena...@geobases.es.gov.br Av. Marechal Mascarenhas de Moraes, 2.524 Jesus de Nazareth, Vitória - ES CEP: 29052-015 -- Antes de imprimir pense em seu compromisso com o meio ambiente. As informações existentes nesta mensagem e em seus arquivos anexados são para uso restrito, sendo seu sigilo protegido por lei. Caso você não seja o destinatário, saiba que leitura, divulgação ou cópia são proibidas. Neste caso, favor notificar o remetente e apagar as informações. O uso impróprio destas informações será tratado conforme as normas da empresa e a legislação em vigor. 2020-01-07 09:23:45,858 WARN [wms.capabilities] - Error writing metadata; skipping layer: trecho_drenagem java.lang.RuntimeException: Error while committing XML elements; specific element was: Start(Layer, org.xml.sax.helpers.AttributesImpl@7f671bfa) at org.geotools.xml.transform.TransformerBase$TranslatorSupport.commit(TransformerBase.java:733) at org.geoserver.wms.capabilities.Capabilities_1_3_0_Transformer$Capabilities_1_3_0_Translator.doHandleLayer(Capabilities_1_3_0_Transformer.java:934) at org.geoserver.wms.capabilities.Capabilities_1_3_0_Transformer$Capabilities_1_3_0_Translator.handleLayerTree(Capabilities_1_3_0_Transformer.java:893) at org.geoserver.wms.capabilities.Capabilities_1_3_0_Transformer$Capabilities_1_3_0_Translator.handleLayers(Capabilities_1_3_0_Transformer.java:727) at org.geoserver.wms.capabilities.Capabilities_1_3_0_Transformer$Capabilities_1_3_0_Translator.handleCapability(Capabilities_1_3_0_Transformer.java:467) at org.geoserver.wms.capabilities.Capabilities_1_3_0_Transformer$Capabilities_1_3_0_Translator.encode(Capabilities_1_3_0_Transformer.java:275) at org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(TransformerBase.java:1026) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.java:300) at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.java:133) at org.geotools.xml.transform.TransformerBase.transform(TransformerBase.java:112) at org.geoserver.wms.capabilities.Capabilities_1_3_0_Response.write(Capabilities_1_3_0_Response.java:49) at org.geoserver.config.CapabilitiesCacheHeadersCallback$RevalidateTagResponse.write(CapabilitiesCacheHeadersCallback.java:143) at org.geoserver.ows.Dispatcher.response(Dispatcher.java:1009) at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:272) at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:174) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:50) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:28) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) at org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:75) at org.geoserver.monitor.MonitorFilter.doFilter(MonitorFilter.java:144) at org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatin
