[opencms-dev] serialization error - Tomcat7 Java 8 OpenCms 9.5.3
Marc Johnson
originalstoic at yahoo.com
Tue Jan 26 12:47:19 CET 2016
Thanks Tobias, I tried as you suggested to first salvage the update by clearing my work folder, but it yielded the exact same results as before, so I then:
1. restored the db
2. restored the original files under webapps
3. recopied the 9.5.3 update folder
4. made sure all permissions for all files/folders were for tomcat in my case tomcat7
5. made the suggested changes in the README
6. made sure all references to the webserver were commented out in opencms-system.xls and the tomcat server.xml file
7. re-ran the update
8. did a comparison of my web xml to restore some particulars
9. restored changes from 6 above
AND NOW ALL WORKING, so this definitely was a bad update procedure on my part and apparently there is a state it gets to where it cannot be restored at least not by just re-running the update process. On Tuesday, January 26, 2016 3:00 AM, Tobias Herrmann <t.herrmann at alkacon.com> wrote:
Hi Marc,
if you take a look into the folder /update/modules/ you can see all the modules provided by the upgrade wizard. The wizard should import all modules with a greater version number than the current module version.
If that did not happen, and the wizard did not offer to upgrade any module, you may want to clear your tomcat work folder and try the update once more. You could also import the given modules using the module management of OpenCms. But this can be tricky, in case you need to import the
org.opencms.workplace module.
Regards,
Tobias
--
Alkacon Software GmbH - The OpenCms Experts
http://www.alkacon.com
http://www.opencms.org
Am 26.01.2016 um 02:49 schrieb Marc Johnson:
> Tobias, when upgrading specific modules via the update as opposed to the fresh install of 9.5.3, would the modules in the Administration page be expected to indicate 9.5.3 version? I do not see one that does. They all say 9.5.0 or 9.5.1. My upgrade went smoothly the second time, but I admit the
> first time screwing it up by leaving the webserver running + references to front end domains in tomcat's server.xml AND opencms-system.xml. This caused the forms in the different stages to redirect improperly. I finished the upgrade by cutting and pasting the correct domain:port at different
> stages and the upgrade finished, but I knew this was going to be problematic.
>
> After fixing config files and re-running the upgrade, it went smoothly, but did I poison the well by going through with the upgrade the wrong way? I can restore my db/config and do it again no problem.
>
>
> On Monday, January 25, 2016 5:35 AM, Tobias Herrmann <t.herrmann at alkacon.com> wrote:
>
>
> Hi,
>
> the deserialization error always indicates, that the version of your opencms.jar does not match the version of the JavaScript resources used by your browser. There is no relation to the tomcat or Java version you are using.
>
> It may be caused either, by an incomplete module import after an update. Or by outdated JavaScript resources in your browser cache. To resolve the first case, please reimport the org.opencms.ade.* modules matching your OpenCms version. Clear your browser cache in any case.
>
> Regards,
>
> Tobias
>
> --
>
> Alkacon Software GmbH - The OpenCms Experts
>
> http://www.alkacon.com <http://www.alkacon.com/>
> http://www.opencms.org <http://www.opencms.org/>
>
> Am 25.01.2016 um 12:07 schrieb Christoph Kukulies:
> > Thanks Marc,
> >
> > at least one other person who got this. Already thought I'm the only one screwing up things :)
> > I'm now going stepwise back. First went back to tomcat_6.0.39 which I had running before
> > and the problem seems to be gone.
> >
> > Am 25.01.2016 um 10:46 schrieb Marc Johnson:
> >> Okay it looks like you got the same errors I did. However my java version did not auto/magically update as yours had + I'm doing my install on a ubuntu machine. I've made my changes on my dev box and will progress through QA/Prod if I can get through it. Otherwise it's back to 9.5.2 for me as
> >> well...
> >>
> >>
> >> On Friday, January 22, 2016 10:15 AM, Christoph Kukulies <kuku at physik.rwth-aachen.de <mailto:kuku at physik.rwth-aachen.de>> wrote:
> >>
> >>
> >> I wiped out my 9.5.3 (updated from 9.5.2) now and did a full 9.5.3 install from the opencms-9.5.3.zip (not update)
> >> and guess what, the problem persists:
> >>
> >>
> >>
> >> This is the picture right after loggin into the workplace:
> >>
> >> http://cms.myserver.de/system/login <http://cms.myserver.de/system/login>and then get to the default page
> >> http://cms.myserver.de/overview
> >>
> >> Help!
> >>
> >> I'm going back to 9.5.2 to see whether it's a java 8 or tomcat 7 issue.
> >> As a side note, I'm using opencms in a ROOT configuration.
> >>
> >> Am 22.01.2016 um 13:34 schrieb Christoph Kukulies:
> >> Another funny thing:
> >>
> >> some sub folders and files have "Publish directly" greyed out and all subfolders are displayed in red.
> >>
> >>
> >>
> >> Am 22.01.2016 um 13:28 schrieb Christoph Kukulies:
> >>> I upgraded an intranet site from 9.5.2 to 9.5.3 today.
> >>> By some mishap the Java installer ran and installed also Java 8. This is Windows 7 btw.
> >>> After that tomcat6 didn't start anymore. I wasn't sure whether this was
> >>> due to the update and some misconfiguration induced by the update or
> >>> if Java 8 was responsible for tomcat6 not starting. So I installed tomcat 7
> >>> and this started smoothly, also Opencms 9.5.3 seems to be running nicely.
> >>>
> >>> Then I started moving some folders around in the workplace.
> >>>
> >>> When trying to publish a freshly moved folder (a normal folder containing subfolders)
> >>> I'm getting now:
> >>>
> >>>
> >>>
> >>> Clearing the browser cache (as suggested above) didn't help. I copied my whole
> >>> webapps/ROOT tree from Tomcat 6.0.39 over to Tomcat 7.0 (while the servlet container was shut down),
> >>> just mentioning it.
> >
> > --
> > Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
> >
> >
> > Am 25.01.2016 um 10:46 schrieb Marc Johnson:
> >> Okay it looks like you got the same errors I did. However my java version did not auto/magically update as yours had + I'm doing my install on a ubuntu machine. I've made my changes on my dev box and will progress through QA/Prod if I can get through it. Otherwise it's back to 9.5.2 for me as
> >> well...
> >>
> >>
> >> On Friday, January 22, 2016 10:15 AM, Christoph Kukulies <kuku at physik.rwth-aachen.de <mailto:kuku at physik.rwth-aachen.de>> wrote:
> >>
> >>
> >> I wiped out my 9.5.3 (updated from 9.5.2) now and did a full 9.5.3 install from the opencms-9.5.3.zip (not update)
> >> and guess what, the problem persists:
> >>
> >>
> >>
> >> This is the picture right after loggin into the workplace:
> >>
> >> http://cms.myserver.de/system/login <http://cms.myserver.de/system/login>and then get to the default page
> >> http://cms.myserver.de/overview
> >>
> >> Help!
> >>
> >> I'm going back to 9.5.2 to see whether it's a java 8 or tomcat 7 issue.
> >> As a side note, I'm using opencms in a ROOT configuration.
> >>
> >> Am 22.01.2016 um 13:34 schrieb Christoph Kukulies:
> >> Another funny thing:
> >>
> >> some sub folders and files have "Publish directly" greyed out and all subfolders are displayed in red.
> >>
> >>
> >>
> >> Am 22.01.2016 um 13:28 schrieb Christoph Kukulies:
> >>> I upgraded an intranet site from 9.5.2 to 9.5.3 today.
> >>> By some mishap the Java installer ran and installed also Java 8. This is Windows 7 btw.
> >>> After that tomcat6 didn't start anymore. I wasn't sure whether this was
> >>> due to the update and some misconfiguration induced by the update or
> >>> if Java 8 was responsible for tomcat6 not starting. So I installed tomcat 7
> >>> and this started smoothly, also Opencms 9.5.3 seems to be running nicely.
> >>>
> >>> Then I started moving some folders around in the workplace.
> >>>
> >>> When trying to publish a freshly moved folder (a normal folder containing subfolders)
> >>> I'm getting now:
> >>>
> >>>
> >>>
> >>> Clearing the browser cache (as suggested above) didn't help. I copied my whole
> >>> webapps/ROOT tree from Tomcat 6.0.39 over to Tomcat 7.0 (while the servlet container was shut down),
> >>> just mentioning it.
> >>
> >>
> >
> > --
> > Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
>
> >
> >
> > _______________________________________________
> > 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/cgi-bin/mailman/listinfo/opencms-dev
> >
> >
> >
>
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
>
> _______________________________________________
> 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/cgi-bin/mailman/listinfo/opencms-dev
>
>
>
>
>
>
>
> _______________________________________________
> 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/cgi-bin/mailman/listinfo/opencms-dev
>
>
>
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
_______________________________________________
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/cgi-bin/mailman/listinfo/opencms-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20160126/e3541e06/attachment.htm>
More information about the opencms-dev
mailing list