&quot;adrian(a)jboss.org&quot; wrote : bind.address:1100 should always be able to see things bound into jndi somewhere in the cluster. | Yes, it works with bind.addres. I was just mentioning that the example uses 'localhost' which would lead to false results if JBoss is bound to a different address. &quot;adrian(a)jboss.org&quot; wrote : | * Use JBoss Messaging to get a proper clustered solution | Would this save me the hassle of doing all the below? &quot;adrian(a)jboss.org&quot; wrote : | 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. | Might you have an example for this? Or need I not do anything except use it (java:/JmsXA) instead of ConnectionFactory? &quot;adrian(a)jboss.org&quot; wrote : | * 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> | | | Thanks for the help! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223069#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...