Hi List,
upgrading to 2.4 (windows server 2008/tomcat), but having a (rather
huge) 2.3 datadirectory, I tested to keep the data directory as is
(pointing to it via environment var).
Reusing my old data_dir, I see a lot of error messages:
"this means the workspace has not yet been added to the catalog, keep
the proxy around"
while Geoserver is running and most layers are ok, there are some (seems
random) shp layers which apperently did not load.
going to the 'stores' in the web interface (to check what was wrong) I
have a 'WicketRuntimeException'...
So trying to be clever 
I thought to test/use the data-dir from the
2.4.0 war. That went fine.
BUT: trying to copy our own 'workspace' and 'data' dir into the data-dir
I end up with the same problems as above.
Googling:
https://github.com/geoserver/geoserver/blob/master/doc/en/user/source/datadirectory/migrating.rst
it seems there seem to be not yet any directions for handling 2.3. to
2.4 upgrade.
Question: is/should it be possible to reuse a 2.3 datadirectory for use
with 2.4
IF yes, what should I change to make it possible?
IF no, anybody an idea how to ease the migration of all my layers to 2.4?
Regards,
Richard Duivenvoorde
On 15-10-13 14:48, Richard Duivenvoorde wrote:
Reusing my old data_dir, I see a lot of error messages:
"this means the workspace has not yet been added to the catalog, keep
the proxy around"
while Geoserver is running and most layers are ok, there are some (seems
random) shp layers which apperently did not load.
going to the 'stores' in the web interface (to check what was wrong) I
have a 'WicketRuntimeException'...
Answering part of my questions myself:
via trail and error: there were 6 layers which in their datastore.xml
were pointing to a Workspace-id (WorkspaceInfoImpl--...) which was not
around (anymore).
Apparently Geoserver 2.3 was ok with? But 2.4 is more strict and raises
those errors...
Regards,
Richard
Hi,
so yeah, theoretically there should be nothing in particular to do, the migration
is automatic.
Not sure what caused 2.4.x to be less lenient than 2.3.x, however those
stores should have not been working in 2.3.x either (the difference
is that 2.3.x started up anyways)
Cheers
Andrea
···
On Tue, Oct 15, 2013 at 4:41 PM, Richard Duivenvoorde <rdmailings@anonymised.com> wrote:
On 15-10-13 14:48, Richard Duivenvoorde wrote:
Reusing my old data_dir, I see a lot of error messages:
“this means the workspace has not yet been added to the catalog, keep
the proxy around”
while Geoserver is running and most layers are ok, there are some (seems
random) shp layers which apperently did not load.
going to the ‘stores’ in the web interface (to check what was wrong) I
have a ‘WicketRuntimeException’…
Answering part of my questions myself:
via trail and error: there were 6 layers which in their datastore.xml
were pointing to a Workspace-id (WorkspaceInfoImpl–…) which was not
around (anymore).
Apparently Geoserver 2.3 was ok with? But 2.4 is more strict and raises
those errors…
Regards,
Richard
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it