The issue has identified as being a failure to apply sticky sessions in the cluster deployment.
"Sticky Sessions" is a method used with Application Load Balancing, to achieve server-affinity. A router or load balancer with sticky-session support can assign a single server to a particular user, based on their HTTP session or IP address. If this is not working the user activity cannot be retrieved and displayed in the Identity portal session.
To workaround this issue shutdown one of the cluster nodes, this will enable the Identity Portal to function as expected, while you configure the cluster to support sticky sessions.
The specific steps require to configure sticky sessions is dependent upon the application host (ie JBoss\Wildfly). Please refer to JBoss\Wildfly product documentation for guidance.