Configure JBoss messaging-activemq as a resource adapter targeting the load-balanced, node-port or headless routes for an AMQ cluster hosted in OpenShift subsystem.xml Deploy an AMQ broker cluster on openshift and expose its endpoint(s) to external clients. Alternative: You can simulate the same failures by configuring the AMQ cluster outside openshift, but in a multihomed environment, using one interface for clustering (node1.internal.test.redhat.com) using plain communication, and another interface for client communication using ssl (sample configs attached). Configure /etc/hosts so that the internal interface is mapped on the broker hosts, but not on the host where JBoss is deployed. Start JBoss EAP and wait some time. You will see UnknownHostExceptions and XARecovery failures as the resource adapter attempts to contact the "internal" broker endpoints.