HA-Singleton JMS not working on secondary cluster nodes in JBoss

Issue

• The application running on the secondary instances are unable to access the destinations running on the primary node which has the HA-Singleton JMS running.

• When the application running on the secondary node attempts to connect to a destination running on the master node, the following exception is thrown:

  javax.naming.NameNotFoundException: XAConnectionFactory not bound
          at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
          at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
          at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
          at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
          at javax.naming.InitialContext.lookup(InitialContext.java:392)
          at org.jboss.util.naming.Util.lookup(Util.java:222)