On Thu, Sep 8, 2011 at 11:32 PM, Ariel Nunez <[email protected]> wrote: > Hello people, > I am experiencing a problem with my GeoServer the GetCapabilities of the WMS > is broken [1]. My questions are: > #1 How can I diagnose which layer is causing this? I end up with a > NullPointerException [2].
More recent versions of Geoserver (2.1.x series) try harder to report the layer name in case of failure. If it's not there and the GS is recent please open a bug report with the full stack trace on jira.codehaus.org > #2 Why does GeoServer return an invalid XML (and XML file inside another XML > file)? I remember some settings about optimizing for speed vs optimizing for > 'correctness' in earlier versions of GeoServer but I don't see that now [3]. The setting is still there where it has always been, in the web.xml file, with a comment explaining the possible values. Would be nice to have it in the GUI in fact, patches welcomed :-) > #3 What changes would be needed in GeoServer to better diagnose (or if > possible self correct) this problem. This is an application where GeoServer > is used as a backend storage and I would like to avoid a failed layer upload > via the REST API from totally breaking the server :( One way would be to harden the REST api against broken input. David also added a validator, WMSValidator, that checked for some layer validity criteria, but it does not check for bounding boxes. Anyways, the idea of disabling the layers might be in the opposite direction as what GeoSolutions intends to propose once we manage to secure funding to improve the existing fault tolerance situation. We routinely get complaints by enterprise customers that a store or a layer "disappeared" after a restart, normally because the data source was not available. What a long running, unattended server needs is to have the caps be able to filter out of the capabilities misbehaving layers/stores without disabling them, so that they come back online as soon as the problem is solved without any manual intervention from the administrator. It might be for example that we run the catalog validators against the layer before starting to encode it in the capabilities, for example. Another thing that we might want to do is to annotate certain fields in the catalog info interfaces as "mandatory", and have a validator complain if one of the fields is missing (thinking about the bbox here). At the moment we're looking for a project to sponsor this kind of development. Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ Why Cloud-Based Security and Archiving Make Sense Osterman Research conducted this study that outlines how and why cloud computing security and archiving is rapidly being adopted across the IT space for its ease of implementation, lower cost, and increased reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
