Here's the default (local) JMSProviderLoader from jms-ds.xml: | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.mq:service=JMSProviderLoader,name=JMSProvider"> | <attribute name="ProviderName">DefaultJMSProvider</attribute> | <attribute name="ProviderAdapterClass"> | org.jboss.jms.jndi.JNDIProviderAdapter | </attribute> | <!-- The combined connection factory --> | <attribute name="FactoryRef">java:/XAConnectionFactory</attribute> | <!-- The queue connection factory --> | <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute> | <!-- The topic factory --> | <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute> | <!-- Uncomment to use HAJNDI to access JMS | <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=localhost:1100 | </attribute> | --> | </mbean> | You should just be able to set one up pointing to your ActiveMQ instance and reference that as your target JMSProviderLoader in the bridge config. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053566#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...