Replying to my own question again in case others encounter this problem.

There's 3 xml files that are stored in the geoserver_data_directory 
named wcs.xml, wfs.xml, and wms.xml.
These files contain basic info on these services and include version 
information for geotools and for WFSInfo - versions. Upgrading to 2.2 
adds a version 2 to these xml files within your data directory. 
Apparently earlier versions of Geoserver throw an error when they get to 
that version 2 in those config files.
I resolved my issue by copying the wcs, wfs, and wms.xml files from 
webapps/geoserver/data and pasting them into my 
geoserver_data_directory, replacing those that had been edited by 
version 2.2.

- Ryan



On 10/26/2012 12:05 PM, Ryan Williams wrote:
> Hi all,
> Working with a Linux CentOS 6 machine here.
> I attempted to upgrade from version 2.1.3 to 2.2 today using the WAR
> method.
> It started fine the first time but the geoserver_data_directory wasn't
> defined so only the 'default' layers that come with geoserver were present.
> I edited the web.xml file to define the geoserver_data_directory and
> then geoserver would not start.
>
> I removed the 2.2 WAR and put the 2.1.3 WAR back in my webapps
> directory, restarted tomcat, and geoserver started fine, but again
> without the geoserver_data_directory being defined.
> I defined the geoserver_data_directory and now version 2.1.3 will not
> start either!
>
> I get an Error listenerStart in my logs.
>
> What would attempting to upgrade to 2.2 have changed in my data directory?
>
> Thanks for any input,
> - Ryan
>

-- 
Ryan Williams
GIS Analyst / Programmer
PAQ Interactive Inc.


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to