Hi.
I deployed a fresh 2.3.1 version of geoserver, tested it and it was working.
But when i change the data dir to the previous that I was using (version 2.3.0), Geoserver fails to start.
Is there a different way to migrate from these minor version changes?
Cheers
What I did:
deployed 2.3.1 war
tested it - (geoserver starts ok)
stopped tomcat
changed datadir parameter
started tomcat
geoserver does not start.
Specs: windows server 2012/tomcat7
Logs:
tomcat last message
SEVERE: The web application [/geoserver] created a ThreadLocal with key of type [org.eclipse.emf.ecore.xml.type.util.XMLTypeUtil.CharArrayThreadLocal] (value [org.eclipse.emf.ecore.xml.type.util.XMLTypeUtil$CharArrayThreadLocal@anonymised.com]) and a value of type [char] (value [[C@anonymised.com]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
http://pastebin.com/0Lj48smQ
geoserver.log last message
2013-04-30 18:41:36,380 WARN [org.springframework.beans.factory.support.DisposableBeanAdapter] - Invocation of destroy method failed on bean with name ‘geoServerLoader’: org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name ‘GWCLifeCycleHandler’: Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)
http://pastebin.com/N56FFmTk
On Wed, May 1, 2013 at 12:20 AM, Diego Felipe <diegosps@anonymised.com> wrote:
Hi.
I deployed a fresh 2.3.1 version of geoserver, tested it and it was working.
But when i change the data dir to the previous that I was using (version
2.3.0), Geoserver fails to start.
Is there a different way to migrate from these minor version changes?
Nope, you should not need to do anything besides pointing it to the
data directory.
However, the errors you showed are ones popping up during a shutdown, and they
are normal when the shutdown follows a failed startup.
Look for the first error messages, the issue is likely there.
Cheers
Andrea
--
GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.
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
-------------------------------------------------------
Found the problem.
As soon as I added the missing plugins (oracle and charts) the instance started up normally.
The old data directory was using Oracle authentication too. So, I guess that was the cause.
However, the previous log contained the hole start up process and nothing related to this problem was mentioned.
Thanks for your help, Andrea.
···
On Wed, May 1, 2013 at 3:58 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Wed, May 1, 2013 at 12:20 AM, Diego Felipe <diegosps@anonymised.com…> wrote:
Hi.
I deployed a fresh 2.3.1 version of geoserver, tested it and it was working.
But when i change the data dir to the previous that I was using (version
2.3.0), Geoserver fails to start.
Is there a different way to migrate from these minor version changes?
Nope, you should not need to do anything besides pointing it to the
data directory.
However, the errors you showed are ones popping up during a shutdown, and they
are normal when the shutdown follows a failed startup.
Look for the first error messages, the issue is likely there.
Cheers
Andrea
–
GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.
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