topic Upgrade 4.2c mt to 4.2d fails in Alfresco Archive

Upgrade 4.2c mt to 4.2d fails

ebogaard — Mon, 09 Sep 2013 10:10:49 GMT

When testing the upgrade of 4.2c multi tenant to 4.2d, it fails.It seems that most SQL-patches are succesfully applied. During startup, I get only two few unusual WARNs: 2013-09-09 11:57:33,433 WARN [admin.patch.AbstractPatch] [AbstractPatch Processor for patch.calendarAllDayEventDatesCorrectingPa

Re: Upgrade 4.2c mt to 4.2d fails

afaust — Mon, 09 Sep 2013 13:09:16 GMT

Hello,

one thing you need to be aware of is that in Alfresco 4.2d the module service does not support a multi-tenancy setup, i.e. it will not execute any module components for tenants. See <a href="https://issues.alfresco.com/jira/browse/ALF-19207">ALF-19207</a> for some details.
I don't know if this affects you, but this has tripped up my upgrade from 4.2c MT to 4.2d MT. My errors were quite different though: The system would start up but the main use case no longer worked. When new tenants were created as a result of a registration form, that transaction always failed since necessary node structures were no longer being initialized.

Regards
Axel

Re: Upgrade 4.2c mt to 4.2d fails

ebogaard — Mon, 09 Sep 2013 15:53:23 GMT

Interesting ticket, but I'm not quite sure what the implications are.
If I understand it right, if I had installed a module, like Records Management, VTI or Trashcan Cleaner, 4.2d doesn't necessarily load those for the tenants. So that means that some models and functionality might be missing. Is that right?

If that is the case, is there a way to force the module to load for every tenant?
How could the not-loading lead to the WARNs and ERRORs I experience?

PS: I fixed the "Could not open Hibernate Session for transaction" ERRORs. Apparently 4.2d uses a lot more connections than <=4.2c did and the available number of connections on the DB-server wasn't in line with what Alfresco was configured for.

Re: Upgrade 4.2c mt to 4.2d fails

afaust — Mon, 09 Sep 2013 16:56:28 GMT

Hello,

the basic understanding of the ticket is not far from the truth. It does not affect "installable modules" such as Records Management or VTI directly or generally, but prevents the execution of instances of the "ModuleComponent" class which may be used to initialize the state of a "installable module" - basically, it prevents some building blocks of modules from being applied to a tenant and the effect is dependent on wether a module uses this kind of building blocks or not.

In 4.2d you can't force a different behaviour. This feature has been disabled at a source level. (I recompiled Alfresco to enable it for me, but this may be risky.)

As far as being the cause of such errors, it fully depends on what these modules - if they even apply to your constellation - are implemented to do and what other code expects them to have done.

Looking closer at the log it also may have nothing to do with your situation (was just meant as a general advisement). It may very well just be an issue with a patch provided by Alfresco which conflicts with a user defined content rule in one of your tenants. I.e. the patch modifies some content, deletes / re-creates nodes and the execution of a rule is attempted on a node that has been deleted during that patch.

It might be worth trying the update with rules completely disabled and re-activating them in a restart afterwards. To disable rules you can modify the ruleService bean found in rule-services-context.xml. If you look at the file, the necessary change should be obvious (in order to not be too cryptic, you need to change the rulesDisabled setting to true).

Regards
Axel

Re: Upgrade 4.2c mt to 4.2d fails

ebogaard — Tue, 10 Sep 2013 12:41:41 GMT

Thanks for your explanation.
I'm going to try this again with the rules disabled and MariaDB with enough connections available.