cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from 3.2r to 3.3

mpinch
Champ in-the-making
Champ in-the-making
Is there a documented upgrade path from 3.2r to 3.3?  We have a heavily customized 3.2r install, but want to go to 3.3 without dumping all of our content.  I'm using and referring to share for the most part. 

Any suggestions on how to go about doing this?
21 REPLIES 21

mrogers
Star Contributor
Star Contributor
The upgrade from 3.2r to 3.3 should be straightforward.   

However
1) make sure you have a backup that works before starting
2) test on a copy of your system first.

http://wiki.alfresco.com/wiki/General_Upgrade_Process

stegbth
Champ in-the-making
Champ in-the-making
Hi,

what is the reason for needing MySQL 5.0.67?
With that requirement a Debian 5 Linux or Ubuntu 8.04LTS Server wont be able to run Alfresco 3.3, as there is only Mysql 5.0.51 included.

greetings
thomas

mrogers
Star Contributor
Star Contributor
I doubt that the version of MySql makes much difference.   Try your version and see how it goes.

v912485
Champ in-the-making
Champ in-the-making
I had no problem upgrading from 3.2r2 to 3.3 using the general upgrade process. However, Share had become become incredibly slow with some pages taking minutes to render whilst others you needed to refresh the page for them to render.
Alfresco explorer on the other hand was working fine without an issue.
I had to roll back to 3.2r2 however since it's Share we use the most.

Anyone else having these problems?
Tnx,
Allan

opoplawski
Champ in-the-making
Champ in-the-making
I'm seeing pages hang completely on certain site wiki dashlets with 3.3.  Removing the dashlet allows more of the page to be displayed, until it hits another dashlet with a problem.  A task in the java process gets cpu bound at the same time so it's stuck doing something.  Is there any kind of debugging that I can turn on that might help track this down?

opoplawski
Champ in-the-making
Champ in-the-making
My issue appears to have been fixed in the 3.3G nightly build.

liefra
Champ in-the-making
Champ in-the-making
Same issue here. After the upgrade the share site gets really slow.

I also noticed that my upgraded Share application does not contain the new repository browser menu item as seen in the "What’s New in Alfresco 3.3 " webcast (see http://blogs.alfresco.com/wp/webcasts/alfresco-webcast-home-page/). Currently not sure if this is related to a configuration setting

opoplawski
Champ in-the-making
Champ in-the-making
It's not enabled by default.  See the install instructions for how to enable.

bnordgren
Champ in-the-making
Champ in-the-making
I've seen many of the same symptoms with my share site after the upgrade to 3.3.  To the list already presented, I'd add that items in the document library are being systemically "modified by" me with a current timestamp. There is no obvious change in the files (maybe it generated a thumbnail for display?), and the only reason I can think of for it to say I'm the one who changed the file would be that my user account was the one which tried to display the site dashboard.

I am also observing an "excessive" amount of java cpu usage. 285 cpu-minutes in the last 1.75-2 hours or so (note: it is using more than one CPU, that's why there's too many minutes). This cpu usage does not seem to be related to the loading of the pages. 

I found that trying to locate a problem dashlet became an exercise in chasing my tail.  I would find a configuration which worked when I was ping-ponging back and forth between "Configure dashboard" and the site's dashboard, but when I'd go to "My Dashboard" and try to return to the site from the "My Sites" dashlet, the page would freeze mid-load. I have not yet found any configuration which loads when I'm linking in from my dashboard.

There is absolutely nothing in the logs except for one line, which popped up the first time I tried to load a site's dashboard:
09:10:12,530 ERROR [org.apache.pdfbox.filter.FlateFilter] Stop reading corrupt stream

Two hours of repeated failure and nothing else is recorded.

Whenever this is fixed, I think it merits a 3.3.1 release.