topic Re: Exception after Upgrade 3.2 -> 3.3 in Alfresco Archive

Exception after Upgrade 3.2 -> 3.3

homer86 — Wed, 26 May 2010 00:18:41 GMT

Hi,I'm relative new to Alfresco, but wanted to try an update from 3.2 to 3.3 today. After installing the new version and configuring, it installed a few patches and after it started regularly I get reproduceable the following exception:03:14:42,537 INFO [org.alfresco.service.descriptor.DescriptorSe

Re: Exception after Upgrade 3.2 -> 3.3

decla — Mon, 21 Jun 2010 05:38:01 GMT

Hi,

Did you find a solution for this issue yet?

Sincerely,
decla

Re: Exception after Upgrade 3.2 -> 3.3

homer86 — Mon, 21 Jun 2010 18:32:45 GMT

Sadly no, I have gone back to 3.2

Re: Exception after Upgrade 3.2 -> 3.3

mdebuan — Wed, 21 Jul 2010 19:46:50 GMT

Hi all,
we are facing the same problem when trying to update from 3.2.0 (2039) to 3.3g.

We see the following effect:
Upgrade from 3.2. to 3.3. works fine and the system reacts as expected. But after working for some days with the repository and then restarting the server, we get the following error:

org.alfresco.service.cmr.version.VersionServiceException: 06030000 The current implementation of the version service does not support the creation of branches.

This error can only be resolved by reimporting the backupped content which is not a solution at all for a productive system :wink:

My colleague found a possible solution here: http://issues.alfresco.com/jira/browse/ALF-2752 but we were not able to implement it. Maybe you have more luck and can support us in uprading :?:

Greetings, Mirko

Re: Exception after Upgrade 3.2 -> 3.3

warlockvix — Wed, 11 Aug 2010 14:47:11 GMT

16:08:45,556 User:cjl ERROR [org.alfresco.fileserver] Caused by: org.alfresco.service.cmr.version.VersionServiceException: 07100000 The current implementation of the version service does not support the creation of branches.

This is with a clean install of 3.3g. Of course, the status of http://issues.alfresco.com/jira/browse/ALF-2752 is Resolved. Anyone else get this and find a solution? Besides what is mentioned in http://issues.alfresco.com/jira/browse/ALF-2752.

Re: Exception after Upgrade 3.2 -> 3.3

dmihelj — Fri, 20 Aug 2010 08:52:28 GMT

16:08:45,556 User:cjl ERROR [org.alfresco.fileserver] Caused by: org.alfresco.service.cmr.version.VersionServiceException: 07100000 The current implementation of the version service does not support the creation of branches.

This is with a clean install of 3.3g. Of course, the status of http://issues.alfresco.com/jira/browse/ALF-2752 is Resolved. Anyone else get this and find a solution? Besides what is mentioned in http://issues.alfresco.com/jira/browse/ALF-2752.

I'm also getting this error and it is very annoying. Didn't find the solution yet though. I will open a JIRA issue.

Re: Exception after Upgrade 3.2 -> 3.3

mrogers — Fri, 20 Aug 2010 10:45:47 GMT

The issue already exists and is ALF-3962

Re: Exception after Upgrade 3.2 -> 3.3

mdebuan — Fri, 03 Sep 2010 09:52:11 GMT

The issue already exists and is ALF-3962

Unfortunately I am not able to find this Issue in JIRA. Maybe you can help me to access the solution?
Greetings, Mirko

Re: Exception after Upgrade 3.2 -> 3.3

marco_altieri — Tue, 28 Sep 2010 10:08:53 GMT

I have the same issue on a 3.3g installation, but I did not upgrade from 3.2.

I found on svn a new version of Version2ServiceImpl.java that seems to manage versioning more accurately.
I'm wondering whether I can recompile only this file. There are possible wrong side-effects ?

Thanks,
Marco

Re: Exception after Upgrade 3.2 -> 3.3

marco_altieri — Thu, 30 Sep 2010 08:20:23 GMT

Versioning seems a bit unstable.
I'm using a "Community v3.3.0 (g 2860) schema 4,100".
I hava a script in "Data Dictionary/Scripts" that is executed on content update.
The updated document has a custom association:


        <association name="bsh:attachment_artwork">
          <source>
            <mandatory>false</mandatory>
            <many>true</many>
          </source>
          <target>
            <class>cm:content</class>
            <mandatory>false</mandatory>
            <many>true</many>
          </target>
        </association>
‍‍‍‍‍‍‍‍‍‍‍‍‍

The script executes the following loop:


        var attachList = document.assocs["bsh:attachment_artwork"];
        if (attachList != null) {
            for (var k = 0; k < attachList.length; k++)  {
                        var attach = attachList[k];
                        attach.save();
                    }
            }
‍‍‍‍‍‍‍‍‍

When, at the end of the script execution, the transaction commits the VersionServiceException is thrown.

Both the updated document and its attachments are versionable.
I removed the versionable aspect from the attachment document and the exception is no more thrown.

It's really difficult to submit a jira ticket because it's difficult to find a repeatable procedure, but I'll try.

I think there is still a bug that is not related to upgrading from 3.2

Re: Exception after Upgrade 3.2 -> 3.3

loftux — Thu, 30 Sep 2010 09:08:44 GMT

Versioning seems a bit unstable.
…
The script executes the following loop:


        var attachList = document.assocs["bsh:attachment_artwork"];
        if (attachList != null) {
            for (var k = 0; k < attachList.length; k++)  {
                        var attach = attachList[k];
                        attach.save();
                    }
            }
‍‍‍‍‍‍‍‍‍

Your code to mee looks like you just trigger a new content update update by doing a save(). So if any of these attachments in itself refers back to you original document you may have a loop. Maybe turn off versioning on property update for the attachments will help. Or is that what your want to achieve?

Re: Exception after Upgrade 3.2 -> 3.3

marco_altieri — Wed, 06 Oct 2010 23:19:51 GMT

Your code to mee looks like you just trigger a new content update update by doing a save(). So if any of these attachments in itself refers back to you original document you may have a loop. Maybe turn off versioning on property update for the attachments will help. Or is that what your want to achieve?

Thanks Loftux!

There is only the relation defined on the main document (with attachments as targets): attachments don't refer back to the main document.

Marco