10 Replies Latest reply on Dec 23, 2013 11:35 PM by mike just

    bridge related: source queue still consumes the jms request

    mike just Master

      I am using JBoss eap 6.1.0 alphal1 version. I am testing the bridge settings in standalone.xml.

       

      Normally the bridge is working fine, which can transfer jms request successfully to the target MDB in another server by the remote-connector.

       

      <bridges>
          <bridge name="test">
              <queue-name>jms.queue.source</queue-name>
              <forwarding-address>jms.queue.destination</forwarding-address>
              <retry-interval>1000</retry-interval>
              <retry-interval-multiplier>1.0</retry-interval-multiplier>
              <reconnect-attempts>-1</reconnect-attempts>
              <static-connectors>
                   <connector-ref>
                        remote-connector
                   </connector-ref>
              </static-connectors>
          </bridge>
      </bridges>
      

       

      But I found one problem: if the source server has the source jms queue defined like below, then I found the jms request will not be transferred to the destination MDB in the target server. It is still consumed by the source MDB in source server. If below queue is not added in source server (standalone.xml), then it is transferred to the destination MDB in target server successfully. I expected it will be forwarded to the destination even if the source queue is defined.

      <jms-queue name="source">
           <entry name="source"/>
      </jms-queue>
      

       

      Is this a normal situation (I did not read related description about this in the hornetq user manual.), or just a bug, or something wrong with my configuration?