topic Migration from 4.2.c to 5.1.g Community in Alfresco Archive

Migration from 4.2.c to 5.1.g Community

joko71 — Mon, 11 Jul 2016 13:19:50 GMT

I'm having a problem with migration on my Win-32 XP Professional VM machine. Server is JBoss 5.1.0 GA with Java 7 JDK and DB is MySQL 5.5.28.We haven't used Solr in 4.2.c.I was kinda expecting that upgrade from 4.2.c to 5.1.g will go pretty smooth.In server.log the first strange occurence was the lo

Re: Migration from 4.2.c to 5.1.g Community

joko71 — Wed, 27 Jul 2016 06:52:40 GMT

Has anyone encountered this loop behavior in upgrade and why that happens?

Here's also my repository.properties file from VM, maybe something in it is causing the behavior.

Re: Migration from 4.2.c to 5.1.g Community

angelborroy — Wed, 27 Jul 2016 07:19:32 GMT

It means that Alfresco cannot upgrade database schema. Try upgrading to 4.2.f or 5.0.d instead of targeting directly 5.1.g

Re: Migration from 4.2.c to 5.1.g Community

joko71 — Fri, 29 Jul 2016 12:26:00 GMT

I tried with 5.0.d first. I've got the same thing as with 5.1.g, the upgrade enters into endless loop. Dissapointing, after so many setuping. Next chance is 4.2.f. 😕

Here's my latest repository properties file, just in case someone notices something wrong.

Re: Migration from 4.2.c to 5.1.g Community

joko71 — Mon, 01 Aug 2016 11:00:00 GMT

I really hoped this upgrade path would work, but no, the same endless loop happens with upgrade attempts to 5.1.g, 5.0.d, and 4.2.f. The last one is surprising to me because our 4.2.c current version is not too far.

Maybe our upgrade past is the problem? It goes like this:

2.1 –> 3.2 –> 3.4.d –> 4.0.d –> 4.2.c

(2.1, 3.2 and 4.2.c were/are working versions, others were just temporaries on upgrade path)

I can try to upgrade it to 4.2.d or 4.2.e and see what will happen, but I'm worried if we're blocked by someting in further upgrades. 😕

Re: Migration from 4.2.c to 5.1.g Community

angelborroy — Tue, 02 Aug 2016 10:11:14 GMT

We have tested these paths: http://www.keensoft.es/en/alfresco-upgrade-paths-for-community-edition/

Hope it helps.

Re: Migration from 4.2.c to 5.1.g Community

joko71 — Mon, 08 Aug 2016 10:24:10 GMT

It seems I solved the problem.

I've found the solution by accident on this page: https://wiki.alfresco.com/wiki/Schema_Upgrade_Scripts

Quote:

<blockquote>
The following properties control the generation and execution of SQL statements to modify the Alfresco schema and data (defaults shown):
db.schema.update=true
db.schema.update.lockRetryCount=24
db.schema.update.lockRetryWaitSeconds=5
db.schema.update=true:

When this is off, Alfresco will not generate or execute any SQL statements. This can be used to completely avoid any metadata queries between upgrades.

db.schema.update.lockRetryCount and db.schema.update.lockRetryWaitSeconds:
If schema updates are on and some modifying SQL has been generated, then the system attempts to get a lock against the database by creating a lock table alf_bootstrap_lock. If the table already exists, the system will wait and repeat the process of metadata examination and script generation. If the lock table cannot be created after all the retry attempts have been exhausted, the system will post a message and exit:
</blockquote>

So, if there is in Alfresco DB lock table, Alfresco will try to perform update defined number of time in a loop, then exit.

For some reason, I had alf_bootstrap_lock table in my Alfresco development DB which I used on my VM. When droppped, 4.2.c –> 4.2.f –> 5.0.d upgrades went just fine. Upgrade 5.0.d –> 5.1.g seems OK, but JBoss stops or freezes when Alfresco WAR is started. Probably is something wrong in web.xml or libraries.

Re: Migration from 4.2.c to 5.1.g Community

joko71 — Mon, 08 Aug 2016 12:08:06 GMT

As I said in previous post, I have a new problem. It seems upgrade is finished, but JBoss stops or freezes when Alfresco WAR is started. I tried to tinker with repository.properties and web.xml but nothing.

Alfresco 5.1.g has different structure than before, that's obvious. I don't know where to look next. One of the changed files is jboss-web.xml. I tried to use it like this:


<?xml version='1.0' encoding='UTF-8'?>

<!DOCTYPE jboss-web PUBLIC
 "-//JBoss//DTD Web Application 4.2//EN"
 "http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd">

<jboss-web>
   <resource-ref>
      <res-ref-name>jdbc/dataSource</res-ref-name>
      <jndi-name>java:alfresco-datasource</jndi-name>
   </resource-ref>

   <resource-ref>
      <res-ref-name>jdbc/activitiIdGeneratorDataSource</res-ref-name>
      <jndi-name>java:alfresco-datasource</jndi-name>
   </resource-ref>
</jboss-web>

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍