topic Migration from 3.0 to 3.3 crashes in Alfresco Archive

Migration from 3.0 to 3.3 crashes

soriaedu79 — Fri, 11 Jun 2010 21:08:09 GMT

Hello,When I tried the migration the following patches failed:- patch.webSiteAddModerated- patch.authorityDefaultZonesPatchThe error is the same in both cases:java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:881) at org.alfresco.repo.site.SiteSe

Re: Migration from 3.0 to 3.3 crashes

soriaedu79 — Fri, 11 Jun 2010 22:20:29 GMT

The last thing I tried is to do the migration with Alfresco Enterprise 3.3 (Trial version)

It doen't work but the message is a little bit different:


Invocation: ReflectiveMethodInvocation: public abstract org.alfresco.service.cmr.repository.ChildAssociationRef org.alfresco.service.cmr.repository.NodeService.createNode(org.alfresco.service.cmr.repository.NodeRef,org.alfresco.service.namespace.QName,org.alfresco.service.namespace.QName,org.alfresco.service.namespace.QName,java.util.Map) throws org.alfresco.service.cmr.repository.InvalidNodeRefException,org.alfresco.service.cmr.dictionary.InvalidTypeException; target is of class [$Proxy10]
org.alfresco.repo.security.permissions.AccessDeniedException: 05110002 Access Denied.  The system is currently in read-only mode.


Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Write operations are not allowed in read-only mode (FlushMode.MANUAL): Turn your Session into FlushMode.COMMIT/AUTO or remove 'readOnly' marker from transaction definition.
‍‍‍‍‍‍‍

I tried to modify the file alfresco/domain/transaction.properties but nothing…

ideas?

Thank you

Re: Migration from 3.0 to 3.3 crashes

loftux — Sat, 12 Jun 2010 05:37:36 GMT

You can not migrate to enterprise if you have not aquired a license. With enterprise you get a 30 day trial, but those 30 days are probably from the day the repository was generated, not when you installed enterprise. After those 30 days it goes into read only mode, and that is what the error message indicates.

Comunity 3.3g is available for download, and you should try that. If that doesn't work going directly from 3.0 to 3.3, try to take it in steps, like 3.0 -> 3.2 -> 3.2r2 -> 3.3.
What exact intermediate versions needed you will have to find out yourself.

Re: Migration from 3.0 to 3.3 crashes

soriaedu79 — Tue, 15 Jun 2010 20:48:02 GMT

Thank you very much Loftux.

I have solved my problems with patches (it was an issue about the root site folder) and from now on, all of them are correctly executed in 3.3 (and 3.3g) versions.

Anyway, the exception regarding to the Hibernate Optimistic Locking is always there so, by the moment, I'm not able to install the 3.3 version.

On the other hand, I have tested the 3.2r version and it works fine!!.

So, I'm going to migrate to the 3.2r version and I'll wait there for a new path upgrade.

Anyone knows if this Is this a bug of the 3.3 version?

Thank you in advance.

Eduardo