bind.address:1100 should always be able to see things bound into jndi somewhere in the cluster. Improvements: * Use hajndi-jms-ds.xml to create a pool of connections (this is what is used in the "all" config anyway) bound at connection factory java:/JmsXA. * Use jndi tricks to use the in-memory connector when co-located with the server in which the singleton jms server is running | <mbean code="org.jboss.naming.LinkRefPairService" | name="jboss.jms:alias=MyConnectionFactory"> | | <!-- jndi binding MyConnectionFactory --> | | <attribute name="JndiName">MyConnectionFactory</attribute> | | <!-- Use TCP/IP when remote --> | | <attribute name="RemoteJndiName">ConnectionFactory</attribute> | | <!-- Use the in-memory connector when local --> | | <attribute name="LocalJndiName">java:/ConnectionFactory</attribute> | <depends>jboss:service=Naming</depends> | </mbean> | * Use JBoss Messaging to get a proper clustered solution View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222638#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...