Issue loading Server Nodes tab after RSA Identity Governance & Lifecycle 7.1.0 installation on WebSphere 9.x clustered environment
Originally Published: 2019-02-06
Last Modified: 2023-10-06
Article Number
Applies To
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.
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:
- With one server node online, the Server Nodes tab loads correctly:
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 :
- In the WebSphere console, from the Resources menu, select JMS > JMSProvider.
- Select appropriate scope from scope selection drop down list.
- Under the selected scope, select the default messaging provider to return to the configuration page.
- Under Additional properties, click Activation specifications.
- Click acmSubscriberActSpec activation specification to return to its properties page.
- In the acmSubscriberActSpec properties page, under the Subscription Durability section check for field Subscription name, which has no value in it.
- Manually type in the value of acmMessageCluster to that field.
- Scroll to the Advanced section below. Place a check next to the option of Always activate MDBs in all servers, as shown below:
- Save the configuration and restart the cluster.
- Verify the Server Node tab is now loading normally.
