PortalInstances out-of-sync adding or removing company on cluster

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.5 CE GA6, 6.2.10 EE GA1, 7.0.0 DXP FP6
• Fix Version/s: 6.2.X EE, 7.0.0 DXP FP14, 7.0.0 DXP SP3, 7.0.3 CE GA4, 7.0.X EE, Master
• Component/s: Core Infrastructure, Fault Tolerance, Fault Tolerance > Clustering Framework, Portal Configuration > Portal Instances
• Labels:
  • liferay-digital-enterprise-70-sp3
  • liferay-fixpack-de-14-7010
  • liferay-fixpack-portal-155-6210
• Branch Version/s:
  7.0.x, 6.2.x
• Backported to Branch:
  Committed
• Story Points: 1.5
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/44649

Steps to Reproduce - 6.2
1. Setup 6.2 cluster (running on localhost:8080 and localhost:9080 - patch level: portal-128
2. Add Portal Instance from Control Panel (ie. virtual host: test) on node1
3. Navigate to Control Panel > User > Roles and click on 'Power user' then on 'Define permission tab'
Checkpoint: you can see the list to default set permission provided to power user role
4. Now login as test user in test:9080 (node2)
5. Navigate to Control Panel > User > Roles and click on 'Power user' then on 'Define permission' tab
Result: empty page is shown apart from the menu bar on the left

---

PortalInstances is a "psuedo" cache of Company information. It is used, for example, by PortalUtil to return configured companies or the default one.

In a cluster environment when you add or remove a company from a node, in the other nodes PortalInstances is not updated.

I've configured a cluster with two nodes and two company (on the left node1 on the right node2). In the homepage a custom portlet will show:

• output of PortalUtil.getCompanyIds
• output of CompanyLocalServiceUtil.getCompanies()
  

On node1 I've added a new instance

New company is visible on PortalInstances on node1

But when I refresh homepage on node2:

• CompanyLocalServiceUtil has the new company
• PortalInstances doesn't have the new company
  

Database is up-to-date. PortalInstances is out of sync.
All the code running on node2 using PortalInstances or PortalUtil will never see the new company.

For example if you install a plugin with a StartupAction on node2 this Startup is runned only on two companies

13:20:44,335 INFO  [localhost-startStop-2][HookHotDeployListener:709] Registering hook for test_instances-portlet
Loading file:/wos1/java/products/bundle625/liferay-portal-6.2-ce-ga6/tomcat-7.0.62/temp/9-test_instances-portlet/WEB-INF/classes/portal.properties
13:20:44,344 INFO  [localhost-startStop-2][TestStartupAction:21] Company 20155:liferay.com
13:20:44,355 INFO  [localhost-startStop-2][TestStartupAction:21] Company 20535:test01.vm.local
13:20:44,355 INFO  [localhost-startStop-2][HookHotDeployListener:851] Hook for test_instances-portlet is available for use
13:20:44,357 INFO  [localhost-startStop-2][PortletHotDeployListener:344] Registering portlets for test_instances-portlet
13:20:44,451 INFO  [localhost-startStop-2][PortletHotDeployListener:492] 1 portlet for test_instances-portlet is available for use

The things will go worst when you remove a company