IDM cache synchronisation issues in Red Hat JBoss Portal cluster
Issue
We are using Red Hat JBoss Portal in a cluster of two nodes.
When a user is updated on one node using the IDM API (org.exoplatform.services.organization.OrganizationService), it takes some time to have the information replicated on the second node (eg: user added to a new Group). We were expecting to have this information replicated almost in real-time, however.
Here are the detailed steps to reproduce the problem:
-
Setup a 2-node portal cluster
-
Connect on node 1 as root
- create a user: UserA
- create groups: Group1, Group2 and Group3
- assign groups Group1 and Group2 to UserA
- create a page Page1 accessible to Group1
- create a page Page2 accessible to Group2
- create a page Page3 accessible to Group3
-
Connect on node 1 with UserA, navigate to Page1 and Page2 --> Keep the session open
-
Connect on node 2 as root and assign groups Group1 and Group3 to UserA
-
With UserA (using already opened session on node 1), refresh the page, navigate to Page1 and Page3 --> This is not working for us: Page 3 never appears in the nav menu and Page 2 is still present in the menu
-
To see the changes, UserA needs to log out and back in on node 1
Environment
- Red Hat JBoss Portal Platform
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.