Re: [Geoserver-users] Latest JRE update problem
On Fri, Mar 15, 2013 at 12:12 PM, Langford, Robert < robert.langf...@salford.gov.uk> wrote: > > > Success, Geoserver working as normal. So I’m guessing that I messed up > with the Geoserver upgrade. Should the upgrade have removed any JAR files > that referenced 2.2.3? I’ve also noticed I have some 2.2.2 JAR files in > that same folder also, could they cause any issues, have I always messed up > upgrades? > This procedure is very likely to mess up upgrades. In order to perform clean upgrades: - setup an external data directory ( http://docs.geoserver.org/latest/en/user/datadirectory/index.html) - when upgrading, uninstall fully the old version and install the new one (and oh, to be on the safe side, also back up the data dir before letting the new GeoServer open it) Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.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 --- -- 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_d2d_mar___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Latest JRE update problem
Abe & Christian - Thank you for you input. All, For clarification I've always only had one path to a JRE in the JAVA_HOME variable. This morning I have; downgraded JRE7 to my last working version (build 1.7.0_15-b03) and ensured environment variable JAVA_HOME was correct, still no joy. As the log file has always has referenced the below, I thought I'd try downgraded Geoserver to my last working version (2.2.3): Error creating bean with name 'wmsDescribeLayer' [...] wms-2.2.5.jar I wasn't sure if you just installed over as if you were upgrading (could someone confirm?) but just went for it; however found same error in log afterwards so removed all JAR files that referenced 2.2.5 (that had a 2.2.3 equivalent) from: ...\webapps\geoserver\WEB-INF\lib Success, Geoserver working as normal. So I'm guessing that I messed up with the Geoserver upgrade. Should the upgrade have removed any JAR files that referenced 2.2.3? I've also noticed I have some 2.2.2 JAR files in that same folder also, could they cause any issues, have I always messed up upgrades? I also upgraded the JRE7 to latest version (build 1.7.0_17-b02), and Geoserver is still working just fine on it. So before I look to upgrading Geoserver to the latest version anything I should do first? Should I go to 2.2.4 then 2.2.5? What about the "old" JAR files, were they the cause of my problems? Should I remove any duplicates or is a clean install needed (preferably not :)). Many thanks, any advice greatly appreciated. Kind regards, Rob From: Langford, Robert Sent: 14 March 2013 15:32 To: 'Andrea Aime'; Jonathan Moules Cc: geoserver-users@lists.sourceforge.net Subject: RE: [Geoserver-users] Latest JRE update problem Jonathan/Andrea - thanks for the information. I've downloaded & installed both the JDK7 & JRE6 and tried changing the JAVA_HOME variable to both directories and stop/started Geoserver. I'm still getting the same error which starts as per the below: 2013-03-14 15:25:50,764 WARN [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!) 2013-03-14 15:25:50,780 ERROR [context.ContextLoader] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wmsDescribeLayer' defined in URL [jar:file:/C:/Program%20Files%20(x86)/GeoServer%202.2.2/webapps/geoserver/WEB-INF/lib/wms-2.2.5.jar!/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.geoserver.wms.DescribeLayer]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.geoserver.wms.DescribeLayer.() [...] Any ideas? Rob From: andrea.a...@gmail.com<mailto:andrea.a...@gmail.com> [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: 14 March 2013 15:26 To: Jonathan Moules Cc: Langford, Robert; geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net> Subject: Re: [Geoserver-users] Latest JRE update problem On Thu, Mar 14, 2013 at 4:16 PM, Jonathan Moules mailto:jonathanmou...@warwickshire.gov.uk>> wrote: So its security-up-to-date now, but the last security patch has been released so will get worse as time goes on (more vulnerabilities, no fixes). Given this, hopefully the GeoServer devs have a plan for updating to Java 7. I think its on their todo list. If the past is any indication, not until most of the production systems around have updated to Java 7. Which does not seem to be the case, at least judging by the servers we have direct access to. That said, the 2.3.x series received some fixes to run on Java 7, but no serious testing. Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.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 --- DISCLAIMER: The information contained in this communication/message from robert.langf...@salford.gov.uk sent on Fri Mar 15 11:12:43 2013 is confidential and may be legally privileged. It is intended solely for the addressee(s) andrea.a...@geo-solutions.it;geoserver-users@lists.sourceforge.net;jonathanmou...@warwickshire.gov.uk Access to this message by anyone else is unauthorised. If you are not the int
Re: [Geoserver-users] Latest JRE update problem
Rob, ... changing JAVA_HOME variable to both directories . I haven't tried this but something like JAVA_HOME=C:\Program Files\Java\jre6;C:\Program Files\Java\jre7 will certainly not work. It is either or. Many of the classes have the same name and what gets loaded at run-time from which jar-file depends very much on alphabet or whatever internal workings of the system. That is precisely the function of the JAVA_HOME to have different JDKs/JREs installed and to keep them separate for different programs. You can have in Windows and Unix/Linux (Don't forget to export in a Unix environment) a system variable to one JRE and overwrite it for a particular program (Jetty/Tomcat) when you want to use the other. Cheers Christian - Dr Christian Maul Project Manager Information Services Branch Department of Sustainability and Environment Level13, Marland House, 570 Bourke Street Melbourne 3000 PO Box 500, East Melbourne Vic 3002 Telephone:+61-3-8636 2325 Telefax: +61-3-8636 2813 -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Latest-JRE-update-problem-tp5040366p5040502.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- 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_d2d_mar ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Latest JRE update problem
I have also been running Geoserver on JRE7. I have two installs of Geoserver running on JRE7 (JRE_1.7.09-b05): GS 2.0.2 installed on Win2008Srvr and GS 2.2.2 deployed in Tomcat on Win2008Srvr. Both are 64bit JVMs. Maybe the issue is with the new Geoserver versions, the later JRE7 versions, the 32bit JRE versions or your individual install or setup. Still lots to check - I'd start at reverting to the older JRE7 version. Abe. -- 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_d2d_mar ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Latest JRE update problem
Jonathan/Andrea - thanks for the information. I've downloaded & installed both the JDK7 & JRE6 and tried changing the JAVA_HOME variable to both directories and stop/started Geoserver. I'm still getting the same error which starts as per the below: 2013-03-14 15:25:50,764 WARN [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!) 2013-03-14 15:25:50,780 ERROR [context.ContextLoader] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wmsDescribeLayer' defined in URL [jar:file:/C:/Program%20Files%20(x86)/GeoServer%202.2.2/webapps/geoserver/WEB-INF/lib/wms-2.2.5.jar!/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.geoserver.wms.DescribeLayer]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.geoserver.wms.DescribeLayer.() [...] Any ideas? Rob From: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: 14 March 2013 15:26 To: Jonathan Moules Cc: Langford, Robert; geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] Latest JRE update problem On Thu, Mar 14, 2013 at 4:16 PM, Jonathan Moules mailto:jonathanmou...@warwickshire.gov.uk>> wrote: So its security-up-to-date now, but the last security patch has been released so will get worse as time goes on (more vulnerabilities, no fixes). Given this, hopefully the GeoServer devs have a plan for updating to Java 7. I think its on their todo list. If the past is any indication, not until most of the production systems around have updated to Java 7. Which does not seem to be the case, at least judging by the servers we have direct access to. That said, the 2.3.x series received some fixes to run on Java 7, but no serious testing. Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.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 --- DISCLAIMER: The information contained in this communication/message from robert.langf...@salford.gov.uk sent on Thu Mar 14 15:32:08 2013 is confidential and may be legally privileged. It is intended solely for the addressee(s) andrea.a...@geo-solutions.it;geoserver-users@lists.sourceforge.net;jonathanmou...@warwickshire.gov.uk Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. As a public body, Salford City Council may be required to disclose this email [or any response to it] under the Freedom of Information Act 2000, unless the information in it is covered by one of the exemptions in the Act. Please immediately contact the sender, robert.langf...@salford.gov.uk if you have received this message in error. For the full disclaimer please access http://www.salford.gov.uk/e-mail. Thank you. -- 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_d2d_mar___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Latest JRE update problem
On Thu, Mar 14, 2013 at 4:16 PM, Jonathan Moules < jonathanmou...@warwickshire.gov.uk> wrote: > So its security-up-to-date *now*, but the last security patch has been > released so will get worse as time goes on (more vulnerabilities, no > fixes). Given this, hopefully the GeoServer devs have a plan for updating > to Java 7. I think its on their todo list. > If the past is any indication, not until most of the production systems around have updated to Java 7. Which does not seem to be the case, at least judging by the servers we have direct access to. That said, the 2.3.x series received some fixes to run on Java 7, but no serious testing. Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.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 --- -- 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_d2d_mar___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Latest JRE update problem
I stand corrected and should read my own wiki link: "Java 6 reached the end of its supported life in February 2013, at which time all updates, including security updates, were scheduled to be stopped.[26][27] Oracle released one more update to Java 6 in March 2013, which patched some security vulnerabilities." So its security-up-to-date *now*, but the last security patch has been released so will get worse as time goes on (more vulnerabilities, no fixes). Given this, hopefully the GeoServer devs have a plan for updating to Java 7. I think its on their todo list. Jonathan On 14 March 2013 15:12, Jonathan Moules wrote: > HI Robert, > I'm far from an expert in Java. But to change which Java Geoserver uses, > change the JAVA_HOME variable: > > http://docs.geoserver.org/stable/en/user/installation/windows/binary.html?highlight=java_home#setting-environment-variables > This way you can have multiple javas installed and specify which to use. > > > Is there any possible issues (security or otherwise) using the old JRE? > Java 6 is still in support I believe, at least for security issues. > https://en.wikipedia.org/wiki/Java_6#Java_6_updates - the last one was > just 10 days ago. > > Jonathan > > > > On 14 March 2013 15:02, Langford, Robert > wrote: > >> Jonathan, >> >> ** ** >> >> Thanks for the info, I’d never heard of any problems like this. >> >> ** ** >> >> How can I change the JRE path for the current installation? I’ll try the >> JDK and if not successful I can try JRE6 (although it definitely was >> working on the last JRE7 version I was using before the update). >> >> ** ** >> >> Is there any possible issues (security or otherwise) using the old JRE?** >> ** >> >> ** ** >> >> Many thanks, >> >> ** ** >> >> Rob >> >> ** ** >> >> *From:* Jonathan Moules [mailto:jonathanmou...@warwickshire.gov.uk] >> *Sent:* 14 March 2013 14:48 >> *To:* Langford, Robert >> *Cc:* geoserver-users@lists.sourceforge.net >> *Subject:* Re: [Geoserver-users] Latest JRE update problem >> >> ** ** >> >> Hi Robert, >> >> I think I saw a thread a few days ago saying that it needed to be the >> JDK for Java 7. >> >> Ah, here we are: >> >> http://sourceforge.net/mailarchive/message.php?msg_id=30581542 >> >> ** ** >> >> I believe the general stance is that Java 7 isn't really supported >> currently. The JDK may work, and JRE6 certainly should. >> >> ** ** >> >> Jonathan >> >> ** ** >> >> ** ** >> >> On 14 March 2013 13:18, Langford, Robert >> wrote: >> >> Hi, >> >> >> >> Today I updated my JRE to: jre-7u17-windows-i586 >> >> >> >> I was running Geoserver 2.2.3 on Win 2008 Server. >> >> >> >> Following the machine restart after the Java install I noticed my >> Geoserver Service hadn’t started. From the logs I found that it wasn ’t >> finding a “valid JRE”. I checked the directory and it appeared the install >> hadn’t worked (lots of files missing) so I reinstalled the JRE and rebooted >> again. >> >> >> >> This time the Geoserver Service started just fine, however when trying to >> access the Web Admin page I got a 503 error. As I was planning on updating >> Geoserver as well (and thought this may solve the issue) I then installed >> 2.2.5; install went fine, installed as a service, valid JRE found. >> >> >> >> However I’m still getting the 503 error. Please see an extract from the >> log below. >> >> >> >> Any assistance would be greatly appreciated. >> >> >> >> Many thanks, >> >> >> >> Rob >> >> >> >> 2013-03-14 12:59:36,620 ERROR [context.ContextLoader] - Context >> initialization failed >> >> org.springframework.beans.factory.BeanCreationException: Error creating >> bean with name 'wmsDescribeLayer' defined in URL >> [jar:file:/C:/Program%20Files%20(x86)/GeoServer%202.2.2/webapps/geoserver/WEB-INF/lib/wms-2.2.5.jar!/applicationContext.xml]: >> Instantiation of bean failed; nested exception is >> org.springframework.beans.BeanInstantiationException: Could not instantiate >> bean class [org.geoserver.wms.DescribeLayer]: No default constructor found; >> nested exception is java.lang.NoSuch
Re: [Geoserver-users] Latest JRE update problem
HI Robert, I'm far from an expert in Java. But to change which Java Geoserver uses, change the JAVA_HOME variable: http://docs.geoserver.org/stable/en/user/installation/windows/binary.html?highlight=java_home#setting-environment-variables This way you can have multiple javas installed and specify which to use. > Is there any possible issues (security or otherwise) using the old JRE? Java 6 is still in support I believe, at least for security issues. https://en.wikipedia.org/wiki/Java_6#Java_6_updates - the last one was just 10 days ago. Jonathan On 14 March 2013 15:02, Langford, Robert wrote: > Jonathan, > > ** ** > > Thanks for the info, I’d never heard of any problems like this. > > ** ** > > How can I change the JRE path for the current installation? I’ll try the > JDK and if not successful I can try JRE6 (although it definitely was > working on the last JRE7 version I was using before the update). > > ** ** > > Is there any possible issues (security or otherwise) using the old JRE?*** > * > > ** ** > > Many thanks, > > ** ** > > Rob > > ** ** > > *From:* Jonathan Moules [mailto:jonathanmou...@warwickshire.gov.uk] > *Sent:* 14 March 2013 14:48 > *To:* Langford, Robert > *Cc:* geoserver-users@lists.sourceforge.net > *Subject:* Re: [Geoserver-users] Latest JRE update problem > > ** ** > > Hi Robert, > > I think I saw a thread a few days ago saying that it needed to be the JDK > for Java 7. > > Ah, here we are: > > http://sourceforge.net/mailarchive/message.php?msg_id=30581542 > > ** ** > > I believe the general stance is that Java 7 isn't really supported > currently. The JDK may work, and JRE6 certainly should. > > ** ** > > Jonathan > > ** ** > > ** ** > > On 14 March 2013 13:18, Langford, Robert > wrote: > > Hi, > > > > Today I updated my JRE to: jre-7u17-windows-i586 > > > > I was running Geoserver 2.2.3 on Win 2008 Server. > > > > Following the machine restart after the Java install I noticed my > Geoserver Service hadn’t started. From the logs I found that it wasn’t > finding a “valid JRE”. I checked the directory and it appeared the install > hadn’t worked (lots of files missing) so I reinstalled the JRE and rebooted > again. > > > > This time the Geoserver Service started just fine, however when trying to > access the Web Admin page I got a 503 error. As I was planning on updating > Geoserver as well (and thought this may solve the issue) I then installed > 2.2.5; install went fine, installed as a service, valid JRE found. > > > > However I’m still getting the 503 error. Please see an extract from the > log below. > > > > Any assistance would be greatly appreciated. > > > > Many thanks, > > > > Rob > > > > 2013-03-14 12:59:36,620 ERROR [context.ContextLoader] - Context > initialization failed > > org.springframework.beans.factory.BeanCreationException: Error creating > bean with name 'wmsDescribeLayer' defined in URL > [jar:file:/C:/Program%20Files%20(x86)/GeoServer%202.2.2/webapps/geoserver/WEB-INF/lib/wms-2.2.5.jar!/applicationContext.xml]: > Instantiation of bean failed; nested exception is > org.springframework.beans.BeanInstantiationException: Could not instantiate > bean class [org.geoserver.wms.DescribeLayer]: No default constructor found; > nested exception is java.lang.NoSuchMethodException: > org.geoserver.wms.DescribeLayer.() > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:997) > > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:943) > > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) > > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) > > > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) > > > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) > > > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(Ab
Re: [Geoserver-users] Latest JRE update problem
Jonathan, Thanks for the info, I'd never heard of any problems like this. How can I change the JRE path for the current installation? I'll try the JDK and if not successful I can try JRE6 (although it definitely was working on the last JRE7 version I was using before the update). Is there any possible issues (security or otherwise) using the old JRE? Many thanks, Rob From: Jonathan Moules [mailto:jonathanmou...@warwickshire.gov.uk] Sent: 14 March 2013 14:48 To: Langford, Robert Cc: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] Latest JRE update problem Hi Robert, I think I saw a thread a few days ago saying that it needed to be the JDK for Java 7. Ah, here we are: http://sourceforge.net/mailarchive/message.php?msg_id=30581542 I believe the general stance is that Java 7 isn't really supported currently. The JDK may work, and JRE6 certainly should. Jonathan On 14 March 2013 13:18, Langford, Robert mailto:robert.langf...@salford.gov.uk>> wrote: Hi, Today I updated my JRE to: jre-7u17-windows-i586 I was running Geoserver 2.2.3 on Win 2008 Server. Following the machine restart after the Java install I noticed my Geoserver Service hadn't started. From the logs I found that it wasn't finding a "valid JRE". I checked the directory and it appeared the install hadn't worked (lots of files missing) so I reinstalled the JRE and rebooted again. This time the Geoserver Service started just fine, however when trying to access the Web Admin page I got a 503 error. As I was planning on updating Geoserver as well (and thought this may solve the issue) I then installed 2.2.5; install went fine, installed as a service, valid JRE found. However I'm still getting the 503 error. Please see an extract from the log below. Any assistance would be greatly appreciated. Many thanks, Rob 2013-03-14 12:59:36,620 ERROR [context.ContextLoader] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wmsDescribeLayer' defined in URL [jar:file:/C:/Program%20Files%20(x86)/GeoServer%202.2.2/webapps/geoserver/WEB-INF/lib/wms-2.2.5.jar!/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.geoserver.wms.DescribeLayer]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.geoserver.wms.DescribeLayer.() at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:997) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:943) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464) at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) at org.geoserver.platform.GeoServerContextLoaderListener.contextInitialized(GeoServerContextLoaderListener.java:18) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:540) at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1220) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:510)
Re: [Geoserver-users] Latest JRE update problem
Hi Robert, I think I saw a thread a few days ago saying that it needed to be the JDK for Java 7. Ah, here we are: http://sourceforge.net/mailarchive/message.php?msg_id=30581542 I believe the general stance is that Java 7 isn't really supported currently. The JDK may work, and JRE6 certainly should. Jonathan On 14 March 2013 13:18, Langford, Robert wrote: > Hi, > > ** ** > > Today I updated my JRE to: jre-7u17-windows-i586 > > ** ** > > I was running Geoserver 2.2.3 on Win 2008 Server. > > ** ** > > Following the machine restart after the Java install I noticed my > Geoserver Service hadn’t started. From the logs I found that it wasn’t > finding a “valid JRE”. I checked the directory and it appeared the install > hadn’t worked (lots of files missing) so I reinstalled the JRE and rebooted > again. > > ** ** > > This time the Geoserver Service started just fine, however when trying to > access the Web Admin page I got a 503 error. As I was planning on updating > Geoserver as well (and thought this may solve the issue) I then installed > 2.2.5; install went fine, installed as a service, valid JRE found. > > ** ** > > However I’m still getting the 503 error. Please see an extract from the > log below. > > ** ** > > Any assistance would be greatly appreciated. > > ** ** > > Many thanks, > > ** ** > > Rob > > ** ** > > 2013-03-14 12:59:36,620 ERROR [context.ContextLoader] - Context > initialization failed > > org.springframework.beans.factory.BeanCreationException: Error creating > bean with name 'wmsDescribeLayer' defined in URL > [jar:file:/C:/Program%20Files%20(x86)/GeoServer%202.2.2/webapps/geoserver/WEB-INF/lib/wms-2.2.5.jar!/applicationContext.xml]: > Instantiation of bean failed; nested exception is > org.springframework.beans.BeanInstantiationException: Could not instantiate > bean class [org.geoserver.wms.DescribeLayer]: No default constructor found; > nested exception is java.lang.NoSuchMethodException: > org.geoserver.wms.DescribeLayer.() > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:997) > > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:943) > > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) > > > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) > > > at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) > > > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) > > > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) > > > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) > > > at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585) > > > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) > > > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464) > > > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385) > > > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284) > > > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) > > > at > org.geoserver.platform.GeoServerContextLoaderListener.contextInitialized(GeoServerContextLoaderListener.java:18) > > > at > org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:540) > > > at > org.mortbay.jetty.servlet.Context.startContext(Context.java:135) > > at > org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1220) > > > at > org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:510)* > *** > > at > org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448) > > at > org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)** > ** > > at > org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerColle
[Geoserver-users] Latest JRE update problem
Hi, Today I updated my JRE to: jre-7u17-windows-i586 I was running Geoserver 2.2.3 on Win 2008 Server. Following the machine restart after the Java install I noticed my Geoserver Service hadn't started. From the logs I found that it wasn't finding a "valid JRE". I checked the directory and it appeared the install hadn't worked (lots of files missing) so I reinstalled the JRE and rebooted again. This time the Geoserver Service started just fine, however when trying to access the Web Admin page I got a 503 error. As I was planning on updating Geoserver as well (and thought this may solve the issue) I then installed 2.2.5; install went fine, installed as a service, valid JRE found. However I'm still getting the 503 error. Please see an extract from the log below. Any assistance would be greatly appreciated. Many thanks, Rob 2013-03-14 12:59:36,620 ERROR [context.ContextLoader] - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'wmsDescribeLayer' defined in URL [jar:file:/C:/Program%20Files%20(x86)/GeoServer%202.2.2/webapps/geoserver/WEB-INF/lib/wms-2.2.5.jar!/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.geoserver.wms.DescribeLayer]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.geoserver.wms.DescribeLayer.() at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:997) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:943) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464) at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) at org.geoserver.platform.GeoServerContextLoaderListener.contextInitialized(GeoServerContextLoaderListener.java:18) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:540) at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1220) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:510) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:222) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977) at sun.reflect.NativeMetho