Thanks for your answer Torsten.
Yes, I have a local consumer, as well as a remote consumer. It sounds like
this is not the correct design to do what I am trying to do (cause the
message to be consumed both on the local server, and the remote server.)
The strategy I am aiming for is write to the local queue, and consume the
message. Then copy to the message to the unreliable remote queue (retrying
until success) then consuming the message there as well.
It sounds like I need two separate queue, each with it's own consumer to
make this succeed? Perhaps setting up a JMS connector with a different
queue name than the local queue will work?
<jmsBridgeConnectors>
<jmsQueueConnector outboundQueueConnectionFactory="#remoteFactory">
<inboundQueueBridges>
<inboundQueueBridge inboundQueueName = "importRequestQueueREMOTE"
localQueueName = "importRequestQueue"/>
</inboundQueueBridges>
<outboundQueueBridges>
<outboundQueueBridge outboundQueueName = "importRequestQueueREMOTE"
localQueueName = "importRequestQueue"/>
</outboundQueueBridges>
</jmsQueueConnector>
</jmsBridgeConnectors>
Then the local server would have a consumer for importRequestQueue, and the
remote server would only have a consumer for importRequestQueueREMOTE.
I don't see how I could create the desired behavior with NetworkConnector,
but perhaps with (Static/Dynamic)IncludedDestinations.
I'll go try that out now. Let me know if there anyone can think a better
way to do this.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-Bridge-trying-to-copy-all-messages-to-remote-server-tp4659769p4659836.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
