I tested the JBossMessaging Bridge (with 1.4.0.CR2) successfully here. I think you made a mistake on the configuration of the remote queue. Here's my remoteserver-jms-ds.xml | <?xml version="1.0" encoding="UTF-8"?> | <server> | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider"> | <attribute name="ProviderName">RemoteJMSProvider</attribute> | <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> | <attribute name="FactoryRef">/XAConnectionFactory</attribute> | <attribute name="QueueFactoryRef">/XAConnectionFactory</attribute> | <attribute name="TopicFactoryRef">/XAConnectionFactory</attribute> | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=remoteservername:1099 | </attribute> | </mbean> | </server> | First check that it's /XAConnectionFactory not XAConnectionFactory. Second, you have to give the address of the remote jndi under java.naming.provider.url, e.g. 192.168.xxx.xxx or server.domain.org I hope this helps... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080955#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...