-
Type:
Bug
-
Status: Verified
-
Resolution: Unresolved
-
Affects Version/s: 6.2.X EE, 7.0.0 DXP SP1, 7.0.X
-
Fix Version/s: None
-
Component/s: Fault Tolerance, Fault Tolerance > Clustering Framework
-
Labels:
-
Fix Priority:2
-
Git Pull Request:
Description:
User Monitoring # Hits and Requests fails to update when Admin is on a different node than user.
A user who is logged onto different node than Admin, does not seem to be tracked by Monitoring, # of Hits stuck on 0, fails to update.
So, although Monitoring shows session of users on other nodes, not all of the data seems to be correctly tracked.
Steps to Reproduce:
In my testing I have two nodes in my cluster with the following properties set in my portal-ext.properties file
cluster.link.enabled=true lucene.replicate.write=true ehcache.cluster.link.replication.enabled=true live.users.enabled=true
1. As my Admin user, I sign into my First Node 9080 and go to User Monitoring.
2. Then as my normal user, I sign into my Second Node 8080.
3. As my Admin user I see the user's session appear, although my user performs actions the # of Hits stays at 0, but I do see the time increase for Last Request.
However Requests and # of Hits do not update for users on different nodes than Admin user.
Results of Testing:
Expected Results: As Admin, able to track # of hits and Requests for all users even if they are on different node than Admin.
Actual Results: As Admin, # of hits and Requests of user fails to update for users on different node than Admin.
Reproduced in?
ee-6.2.x Yes, reproduced in 6.2.x. Request and # hits not updated for user on different node.
Git ID: a0271cfefb983d07c067df46a7685e419507dbfa
ee-7.0.x Yes, reproduced in 7.0.x.
Git ID: c409ef241b005bb0870b3850ed1ae2cefd1d892f