3.0 -> 3.3 Upgrade Problem - PatchExecuter [SOLVED]

luca — Fri, 14 May 2010 10:32:58 GMT

Hi all,I have a problem upgrading Alfresco 3.0 to Alfresco 3.3. From the log I can see that PathExecuter is looping in his attemps to to migrate old-style content URL storage to the newer alf_content_url storage, as I can understand from ContentUrlConverterPatch that is the class that log it. It rea

Re: 3.0 -> 3.3 Upgrade Problem - PatchExecuter [SOLVED]

luca — Thu, 20 May 2010 08:03:52 GMT

I found what was causing all the troubles!

You have to increase this value:
-> max_locks_per_transaction <-

We are using Postgres 8.1 and the patch ContentUrlConverter had to write about 45000 records on alf_content_url but at about 35500 record it run out of locks and it gave me this error:


org.springframework.dao.DataAccessResourceFailureException: SqlMapClient operation; SQL [];   
— The error occurred in alfresco/ibatis/#resource.dialect#/content-insert-SqlMap.xml.  
— The error occurred while applying a parameter map.  
— Check the alfresco.content.insert_ContentUrl-InlineParameterMap.  
— Check the statement (update failed).  
— Cause: org.postgresql.util.PSQLException: ERROR: out of shared memory; nested exception is com.ibatis.common.jdbc.exception.NestedSQLException:   
— The error occurred in alfresco/ibatis/#resource.dialect#/content-insert-SqlMap.xml.  
— The error occurred while applying a parameter map.  
— Check the alfresco.content.insert_ContentUrl-InlineParameterMap.  
— Check the statement (update failed).  
— Cause: org.postgresql.util.PSQLException: ERROR: out of shared memory
‍‍‍‍‍‍‍‍‍‍‍‍‍

I want to poin out that Alfresco doesn't log it and simply restart to cycle in the contentstore from the beginning again and this is not the behaviour that I was expecting!! :evil:

I had to go in debugging mode to found it and replycating this took an entire day, I hope this could be usefull for others that run in this issue.

Re: 3.0 -> 3.3 Upgrade Problem - PatchExecuter [SOLVED]

louise — Fri, 04 May 2012 18:37:40 GMT

Same effect with 4.0.d…

Just try to increase "max_locks_per_transaction" to "128" in file "/opt/alfresco/alf_data/postgresql/postgresql.conf" …

topic Re: 3.0 -> 3.3 Upgrade Problem - PatchExecuter [SOLVED] in Alfresco Archive

3.0 -> 3.3 Upgrade Problem - PatchExecuter [SOLVED]

Re: 3.0 -> 3.3 Upgrade Problem - PatchExecuter [SOLVED]

Re: 3.0 -> 3.3 Upgrade Problem - PatchExecuter [SOLVED]