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

Solution Verified - Updated -

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)
    

Environment

JBoss Enterprise Application Platform (EAP)

  • 5.0.x
  • 5.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.