When configuration JMS bridge between 2 servers and "jms/RemoteConnectionFactory" is set to be used in "source" server then it cannot be found. Connfiguration for JMS bridge: <subsystem xmlns="urn:jboss:domain:messaging:1.3"> <hornetq-server> ... </hornetq-server> <jms-bridge name="myBridge"> <source> <connection-factory name="jms/RemoteConnectionFactory"/> <destination name="jms/queue/InQueue"/> </source> <target> <connection-factory name="jms/RemoteConnectionFactory"/> <destination name="jms/queue/OutQueue"/> <context> <property key="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/> <property key="java.naming.provider.url" value="remote://192.168.40.1:4447"/> </context> </target> <quality-of-service>AT_MOST_ONCE</quality-of-service> <failure-retry-interval>1000</failure-retry-interval> <max-retries>-1</max-retries> <max-batch-size>10</max-batch-size> <max-batch-time>100</max-batch-time> <add-messageID-in-header>true</add-messageID-in-header> </jms-bridge> ... </subsystem> Deploying JMS bridge fails with: JBAS014775: New missing/unsatisfied dependencies: service jboss.naming.context.java.jms.RemoteConnectionFactory (missing) dependents: [service jboss.messaging.jms-bridge.myBridge] It works when ConnectionFactory or java:jboss/exported/jms/RemoteConnectionFactory is used instead.
That is not an issue. If there is no <context> defined, the JMS Bridge will use an InitialContext local to the server. The RemoteConnectionFactory lookup is for external use. If the lookup is local to the server, the JMS Bridge should instead use the /ConnectionFactory lookup that will return a ConnectionFactory tailor-made for in-vm communication.
Ok, there is misconfiguration. I just forgot to add: <entry name="jms/RemoteConnectionFactory"/> to configuration of RemoteConnectionFactory. It works now. Closing bz.