5 Replies Latest reply on Jul 6, 2009 10:03 AM by Eric Turner

    Stand-Alone Messaging: Trouble Configuring a Core Bridge

    Eric Turner Newbie

      I'm trying to set up a simple core bridge from a queue on server0 to a queue on server1 using JBoss 2.0.0 BETA3, and can't seem to make it work. Both JMS servers start, but when I put messages on the queue with my producer on server0 the messages are never read by the consumer on server1. Any ideas why? If I run producer and consumer on the same host the consumer receives all of the messages produced, so I know each server works by itself. The problem is with the bridging. Also interesting is that if I change the "remote" connector port in the server0 configuration it complains, so I know server0 is making some sort of connection to server1.

      The config files for server0 (forgive typos, I have to re-type the config files here because I can't access the Internet from the system I'm working on):

      jbm-jms.xml

      <configuration xmlns="urn:jboss:messaging"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:jboss:messaging /schema/jbm-jms.xsd">
       <connection-factory name="ConnectionFactory">
       <connector-ref connector-name="netty" />
       <entries>
       <entry name="ConnectionFactory" />
       </entries>
       </connection-factory>
       <queue name="amessage">
       <entry name="/queue/amessage" />
       </queue>
      </configuration>
      


      jbm-configuration.xml
      <configuration xmlns="urn:jboss:messaging"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:jboss:messaging /schema/jbm-configuration.xsd">
       <clustered>true</clustered>
       <connectors>
       <connector name="netty">
       <factory-class>org.jboss.messaging.integration.transports.netty.NettyConnectorFactory</factory-class>
       <param key-"jbm.remoting.netty.port" value="5445" type="Integer" />
       </connector>
       <connector name="remote">
       <factory-class>org.jboss.messaging.integration.transports.netty.NettyConnectorFactory</factory-class>
       <param key-"jbm.remoting.netty.port" value="5446" type="Integer" />
       <param key-"jbm.remoting.netty.host" value="server1" type="Strnig" />
       </connector>
       </connectors>
       <acceptors>
       <acceptor name="netty">
       <factory-class>org.jboss.messaging.integration.transports.netty.NettyAcceptorFactory</factory-class>
       <param key-"jbm.remoting.netty.port" value="5445" type="Integer" />
       </acceptor>
       </acceptors>
       <queues>
       <queue name="jms.queue.amessage">
       <address>jms.queue.amessage</address>
       </queue>
       </queues>
       <bridges>
       <bridge name="server1-amessage-bridge">
       <queue-name>jms.queue.amessage</queue-name>
       <forwarding-address>jms.queue.amessage</forwarding-address>
       <connector-ref connector-name="remote" />
       </bridge>
       </bridges>
       <security-enabled>false</security-enabled>
      </configuration>
      


      The configuration for server1:

      jbm-jms.xml is identical to that for server0.

      jbm-configuration.xml
      <configuration xmlns="urn:jboss:messaging"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="urn:jboss:messaging /schema/jbm-configuration.xsd">
       <clustered>true</clustered>
       <connectors>
       <connector name="netty">
       <factory-class>org.jboss.messaging.integration.transports.netty.NettyConnectorFactory</factory-class>
       <param key-"jbm.remoting.netty.port" value="5446" type="Integer" />
       </connector>
       </connectors>
       <acceptors>
       <acceptor name="netty">
       <factory-class>org.jboss.messaging.integration.transports.netty.NettyAcceptorFactory</factory-class>
       <param key-"jbm.remoting.netty.port" value="5446" type="Integer" />
       </acceptor>
       </acceptors>
       <security-enabled>false</security-enabled>
      </configuration>