bridge related: source queue still consumes the jms request

[ohmygod]

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?

[jbertram]

Please elaborate on the MDB configuration on the source server (e.g. attach the activation configuration properties).

Also, please elaborate as to why you're using EAP 6.1 alpha when GA/Final builds of 6.1 and 6.2 are available for download.

[ohmygod]

The reason why I am using EAP 6.1. alpha is because our project is using this version. It has not got a chance to upgrade to a newer GA/Final version.

Source MDB on source server:

@MessageDriven(messageListenerInterface = MessageListener.class, activationConfig =
{
        @ActivationConfigProperty(propertyName = "destination", propertyValue = "source"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
@TransactionManagement(value = TransactionManagementType.BEAN)

target MDB on target server:

@MessageDriven(messageListenerInterface = MessageListener.class, activationConfig =

{

        @ActivationConfigProperty(propertyName = "destination", propertyValue = "target"),

        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })

@TransactionManagement(value = TransactionManagementType.BEAN)

[ohmygod]

Hi Justin,

If you can help confirm this is a hornetq bug in 6.1.0 alpha version, I will ignore it and walk aournd it by not defining the source queue on source server, because so far I found the bridge works well if there is no source queue defined on server server.

[jbertram]

It looks to me like you're simply creating competing consumers for the "source" queue.  You have both a bridge and an MDB consuming from the "source" queue.  Since only one consumer can receive a message from a queue if the MDB consumes the message then the bridge won't be able to. 

My guess is that if you define the <jms-queue> you allow the MDB to actually deploy and consume messages.

[jbertram]

At this point I don't think it's a bug.

[ohmygod]

Then how could this happen? I can not find anything unusual configuration which caused this. Do you have any idea?

[jbertram]

Did you read my other reply on this thread?

[ohmygod]

Sorry, I missed reading your first reply. Then you think how to resolve this situation? Any method to fix this(just let bridge forward the message instead of letting source queue consumes it) if the source queue is also defined?

[jbertram]

I believe I've already provided the basic answer to your question, but I'll summarize again to be clear...

In essence, the bridge is just a message consumer - it consumes messages from a "source" queue and forwards them to a "destination" address.  The MDB is just a consumer as well.  Therefore, if you want the bridge to always forward every message sent to the queue then you shouldn't also have an MDB consuming messages from that same queue because only one of them (either the bridge or the MDB) can get the message.  That's the basic semantics of a queue. 

I can't really advise you beyond that without knowing more about your application architecture and functional priorities.

[ohmygod]

I see. Thanks for the detailed explanation.

When you have time ,can you also ake a look at another problem I am seeing? Thanks in advance.

bridge related: not working between source server and target server from a Vitual machine