[opencms-dev] Open CMS 8 Upgrade Problem
Dawn Louis
dawn.louis at ibsplc.com
Tue May 31 15:42:48 CEST 2011
Hi Michael,
Thanks for the reply.
This change worked and i was able to complete the update process. But in the
WEB-INF/logs/update.log, i get the following error,
java.lang.AbstractMethodError
at
org.opencms.configuration.A_CmsXmlConfiguration.<init>(A_CmsXmlConfiguration.java:62)
at
com.bearingpoint.opencms.commons.springmanager.SpringManagerConfiguration.<init>(SpringManagerConfiguration.java:114)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at
org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:206)
at org.apache.commons.digester.Rule.begin(Rule.java:175)
at
org.apache.commons.digester.Digester.startElement(Digester.java:1453)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1765)
at
org.opencms.configuration.CmsConfigurationManager.loadXmlConfiguration(CmsConfigurationManager.java:506)
at
org.opencms.configuration.CmsConfigurationManager.loadXmlConfiguration(CmsConfigurationManager.java:342)
The application cannot be accessed due to this error.
FYI : In the existing application, we have added the com.bearingpoint module
to introduce the workflow management. Please advise if we should remove the
bearingpoint module before we proceed with the update process?
Michael Emmerich-2 wrote:
>
> Dawn,
>
> this sounds as if the url you enter tries to start OpenCms and not the
> update wizard. Therefore it says (correctly) that the wizard is still
> enabled.
>
> In a normal installation, the path to OpenCms is
>
> [servername]/[webapplicationname]/opencms/some_path_in_opencms
>
> The Update folder is just a folder in your webapplication, therefore the
> path to it is
>
> [servername]/[webapplicationname]/update
>
> Without the "opencms", because this would try to access the OpenCms
> servlet and this is not what we want for the update.
>
> From the URL you send, it does seems as if you try to access the tomcat
> directly, therefore, no apache rewrite rules should try to insert the
> "opencms" in the path.
>
> Kind Regards,
> Michael.
>
>
>
> Am 30.05.2011 15:21, schrieb Dawn Louis:
>>
>> Hi Michael,
>>
>> Thanks for the reply.
>>
>> I did the change as was mentioned in the post.
>>
>> - Restored a backup (Web application and the CMS db) and started the CMS
>> servlet container.
>> - Deselected the "Use Upload Applet" option in the OpenCMS User
>> Preferences
>> (as mentioned in
>> http://mail.opencms.org/pipermail/opencms-dev/2007q1/027888.html)
>> - Verified the User Management>> User properties to ensure that the
>> entry
>> "USERPREFERENCES_workplace-generaloptionsuploadapplet at
>> java.lang.Boolean=false"
>> is not present. (as mentioned in
>> http://lists.opencms.org/pipermail/opencms-dev/2011q2/035708.html)
>> - The index generation has been disabled, the files opencms.properties
>> and
>> cmsupdate.ori were modified as mentioned in the readme file.
>>
>> The servlet container was started and the same error(Critical error
>> during
>> OpenCms initialization: The OpenCms setup wizard is still enabled) is
>> found
>> in the cms log.
>>
>> The following error message is shown in the browser,
>> "HTTP Status 500. OpenCms is not properly initialized!
>> Please make sure that the OpenCms setup wizard has been run once and is
>> disabled now"
>>
>> Could you please advise as to what was done wrong?
>>
>> Regards,
>> Dawn
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Michael Emmerich-2 wrote:
>>>
>>> Hello Dawn,
>>>
>>> try
>>>
>>> http://localhost:8080/applicaitonname/update/
>>>
>>> this should start the updater.
>>>
>>> And before updating, please check if the Admin user has non default
>>> settings for the upload-applet as I wrote in some other postes.
>>>
>>> Kind regards,
>>> Michael
>>>
>>> Am 30.05.2011 08:11, schrieb Dawn Louis:
>>>>
>>>> Hi
>>>>
>>>> I have an application deployed in Jboss 5.1.0, MYSql database
>>>> with
>>>> Open
>>>> CMS 7.5.2. In order to upgrade the application to CMS 8, I had copied
>>>> the
>>>> UPDATE folder and WEB-INF folder to the applications root folder.
>>>>
>>>> I had then, modified the existing opencms.properties file to have
>>>> the
>>>> value of wizard.enabled=true. I had then disabled the index
>>>> generation
>>>> by
>>>> removing the entries in cmsupdate.ori file, as was specified in the
>>>> readme.txt file.
>>>>
>>>> I then restarted the jboss server, and tried to access the URL
>>>> http://localhost:8080/applicaitonname/opencms/update/
>>>>
>>>> But I got the following message in the browser
>>>> "HTTP Status 500
>>>> OpenCms is not properly initialized!
>>>> Please make sure that the OpenCms setup wizard has been run once and is
>>>> disabled now."
>>>>
>>>> The cms log files have this entry
>>>> "[2011-05-27 18:16:07,745 414229] [INFO ] [STDOUT] - [2011-05-27
>>>> 18:16:07,745]- Critical error during OpenCms initialization: The
>>>> OpenCms
>>>> setup wizard is still enabled.
>>>> org.opencms.main.CmsException: Critical error during OpenCms
>>>> initialization:
>>>> The OpenCms setup wizard is still enabled.
>>>> at
>>>> org.opencms.main.OpenCmsCore.setErrorCondition(OpenCmsCore.java:341)
>>>> at
>>>> org.opencms.main.CmsInitException.setErrorCondition(CmsInitException.java:121)
>>>> at org.opencms.main.CmsInitException.<init>(CmsInitException.java:78)
>>>> at org.opencms.main.CmsInitException.<init>(CmsInitException.java:64)
>>>> at org.opencms.main.OpenCmsCore.initContext(OpenCmsCore.java:1305)
>>>> at org.opencms.main.OpenCmsCore.upgradeRunlevel(OpenCmsCore.java:1876)
>>>> at org.opencms.main.OpenCmsServlet.init(OpenCmsServlet.java:248)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048)
>>>> at
>>>> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
>>>> at
>>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
>>>> at
>>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>>> at
>>>> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
>>>> at
>>>> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
>>>> at
>>>> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
>>>> at
>>>> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
>>>> at
>>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>>> at
>>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>>> at
>>>> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
>>>> at
>>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>>> at
>>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
>>>> at
>>>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
>>>> at
>>>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
>>>> at
>>>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>>>> "
>>>>
>>>> I had removed the work and temp folders, but still the same
>>>> error
>>>> occurs.
>>>>
>>>> Could you please advise as to what was done wrong.
>>>>
>>>> Thanks
>>>> Dawn
>>>>
>>>>
>>>
>>> --
>>> Kind Regards,
>>> Michael.
>>>
>>> -------------------
>>> Michael Emmerich
>>>
>>> Alkacon Software GmbH - The OpenCms Experts
>>> http://www.alkacon.com - http://www.opencms.org
>>>
>>> _______________________________________________
>>> This mail is sent to you from the opencms-dev mailing list
>>> To change your list options, or to unsubscribe from the list, please
>>> visit
>>> http://lists.opencms.org/mailman/listinfo/opencms-dev
>>>
>>>
>>
>
> --
> Kind Regards,
> Michael.
>
> -------------------
> Michael Emmerich
>
> Alkacon Software GmbH - The OpenCms Experts
> http://www.alkacon.com - http://www.opencms.org
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
--
View this message in context: http://old.nabble.com/Open-CMS-8-Upgrade-Problem-tp31715346p31740936.html
Sent from the OpenCMS - Dev mailing list archive at Nabble.com.
More information about the opencms-dev
mailing list