Wildfly/Jboss cluster isolation configuration tips

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

We use Multicast for the cluster, which was specified during the IDM install, and modified the standalone.sh to set the MULTI_CAST_ADDRESS to the address that was given to us by the network. We have 4 states. Test, DEV, TRANS and PROD. So far we've set up Test and DEV, using their own Multicast address, but we see references to Test server in DEV's server log, for example when Test IDM is shut down.

In other words, some other process like HornetQ is ignoring the Multicast address we provide in the standalone.sh and finding a node (test) in a different Multicast address. Because of this issue, when we submit a task in DEV, it's stuck In Progress state forever. Are there any other post-install steps we need to take to set up clustering in wildfly or IDM? 

Environment

Release:
Component: IDMGR

Resolution

JBoss/Wildfly clusters are very sensitive to cross-cluster interference when jgroups and other configuration artifacts are not unique to each cluster. This cross-cluster interference is exactly what you are experiencing.

Ensure each cluster is on a different subnet.

Also, see the attached document, IM Clustering on JBoss - Resolving failover issues, which was created by our Sustaining Engineering team and has been helpful in resolving cluster issues.

Though the CA installer only creates a default cluster, and we do not provide additional configuration support for Wildfly/JBoss, the attached doc has been reported by customers to have been very helpful in isolating clusters.

Please note that your Wildfly/Jboss version may have different clustering requirements or artifacts than specified in the document, so consider it to be a general guide in principle only.

For further assistance with clustering issues contact your JBoss/Wildfly application support.