Hi list,

I have discovered that WFS GetCapabilities request is failing in
GeoServer...
After investigating it seems that our workspace naming convention might be
responsible for this, let me explain it.

After discovering this issue I read in the list that a misconfigured layer
can cause this problems and going to Settings, Global and selecting the
option below it will allow WFS capabilities document to be shown and the
misconfigured layer/s will appear in the log:
<http://osgeo-org.1560.x6.nabble.com/file/n5299017/Capture1.png> 

Applying this I went to the log and surprisingly the size was increasing
very quickly, looking at it most of the layers were being display on the log
along with the error...

2016-12-06 15:18:20,176 WARN [wms.capabilities] - Error writing metadata;
skipping layer: rapideye_20151022_120426_NDVI
java.lang.RuntimeException: Error while committing XML elements; specific
element was: Start(Layer, org.xml.sax.helpers.AttributesImpl@7682e3c6)
        at
org.geotools.xml.transform.TransformerBase$TranslatorSupport.commit(TransformerBase.java:733)
        at
org.geoserver.wms.capabilities.GetCapabilitiesTransformer$CapabilitiesTranslator.handleLayerTree(GetCapabilitiesTransformer.java:827)
        at
org.geoserver.wms.capabilities.GetCapabilitiesTransformer$CapabilitiesTranslator.handleLayers(GetCapabilitiesTransformer.java:714)
        at
org.geoserver.wms.capabilities.GetCapabilitiesTransformer$CapabilitiesTranslator.handleCapability(GetCapabilitiesTransformer.java:462)
        at
org.geoserver.wms.capabilities.GetCapabilitiesTransformer$CapabilitiesTranslator.encode(GetCapabilitiesTransformer.java:299)
        at
org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(TransformerBase.java:1026)


......

So I went to workspaces edit but did NOT edit anything just clicked "Save"
and got this error:
<http://osgeo-org.1560.x6.nabble.com/file/n5299017/Capture2.png> 

So to me it looks workspace naming has to start with a letter...???

All the workspaces and layers were ingested to GeoServer using rest, hence
no warnings about this before.

Another question is: Why is just failing WFS getCapabilities request?? WMS
and WCS are working fine (even though we have this warnigns in the log for
those too...)

Any help would be really appreciate it.

Thanks,

Alberto




--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Workspace-naming-convention-disable-WFS-getCapabilities-tp5299017.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to