000037170 - Issue loading Server Nodes tab after RSA Identity Governance & Lifecycle 7.1.0 installation on WebSphere 9.x clustered environment

Document created by RSA Customer Support Employee on Apr 25, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037170
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition:  7.1.0+
Platform:  WebSphere 9.0.0.9
Issue
After installing RSA Identity Governance & Lifecycle 7.1.0 (technically 7.1_P01) on WebSphere, then navigating to the Server Nodes tab to check status of the servers, if only one application server is running,the view shows up immediately. 

When both server nodes are started, the table view hangs for a very long time and eventually returns the state of the servers.

 


  • With two server nodes online, the Server Nodes tab hangs with the message Loading Data, as shown:

User-added image


  • With one server node online, the Server Nodes tab loads correctly:

User-added image


 
Cause
The Java Message Service (JMS) provider configuration settings are missing for the WebSphere Application Server (WAS) 9 clustering.


 
Resolution

Configure a Java Message Service (JMS) Provider


Under JMS providers navigate to  Default Messaging Provider  > Activation Specification > acmSubscriberActSpec.

Subscription Name: acmMessageCluster

Also make sure you have checked the option Always activate MDBs in all servers in Advanced section as shown below : 
 
  1. In the WebSphere console, from the Resources menu, select JMS > JMSProvider.
  2. Select appropriate scope from scope selection drop down list.
  3. Under the selected scope, select the default messaging provider to return to the configuration page. 


User-added image


  1. Under Additional properties, click Activation specifications.
  2. Click acmSubscriberActSpec activation specification to return to its properties page.  
  3. In the acmSubscriberActSpec properties page, under the Subscription Durability section check for field Subscription name, which has no value in it.
  4. Manually type in the value of acmMessageCluster to that field.
  5. Scroll to the Advanced section below.  Place a check next to the option of Always activate MDBs in all servers, as shown below:


User-added image


  1. Save the configuration and restart the cluster.
  2. Verify the Server Node tab is now loading normally.

Attachments

    Outcomes