Thanks again for the help.
Andrea was right.. for some reason the wfs.xml looked like this:
(Version numbers are the same...??)
V_11
XML
true
V_11
URN
false
After changing the first V_11 to V_10
You can check you disk space. I have this kind of issue when there is no
space on the hard disk :/
We just copy-pasted the empty files from a fresh install of GeoServer to the
GeoServer's project. We had lucky I think because all worked after :)
Y.
2011/10/19 Andrea Aime
> On Wed, Oct 19, 2011
On Wed, Oct 19, 2011 at 10:34 AM, Sjoerd Brandsma wrote:
> Hi,
>
> Thanks for the quick reply.
>
> This geoserver configuration is mainly used serving WMS and WFS from a
> postgis DB.
> The datastore/layer configuration doesn't change often and we're not
> using the REST interface.
>
> I've reload
Hi,
Thanks for the quick reply.
This geoserver configuration is mainly used serving WMS and WFS from a
postgis DB.
The datastore/layer configuration doesn't change often and we're not
using the REST interface.
I've reloaded the configuration multiple times. Restarted all the
tomcat instances tha
On Wed, Oct 19, 2011 at 10:12 AM, Sjoerd Brandsma wrote:
> Hi,
>
> After running months without any problems a multi tomcat/geoserver
> environment running 8 tomcats with 8 geoservers behind IIS with AJP13
> I cannot acces WFS data / WFS admin page anymore.
>
Something is really wrong in the in m
Hi,
After running months without any problems a multi tomcat/geoserver
environment running 8 tomcats with 8 geoservers behind IIS with AJP13
I cannot acces WFS data / WFS admin page anymore.
Stack trace when trying to acces the WFS admin page:
2011-10-19 10:05:02,270 ERROR [org.apache.wicket.Req
