Hi,
I am trying to network a satellite application broker to the central broker.
The network connectors and forwarding rules are configured on the central
brokers like so:
<destinationInterceptors>
<virtualDestinationInterceptor>
<virtualDestinations>
<compositeQueue name="app.out">
<forwardTo>
<queue physicalName="app.in"/>
</forwardTo>
</compositeQueue>
</virtualDestinations>
</virtualDestinationInterceptor>
</destinationInterceptors>
<networkConnectors>
<networkConnector name="app-subscriber"
uri="static:tcp://appbroker:61616" userName="admin" password="admin"
duplex="false" staticBridge="true" networkTTL="5">
<staticallyIncludedDestinations>
<queue physicalName="app.in"/>
</staticallyIncludedDestinations>
</networkConnector>
<networkConnector name="app-publisher"
uri="static:tcp://appbroker:61616" userName="admin" password="admin"
duplex="true" staticBridge="true" networkTTL="5">
<staticallyIncludedDestinations>
<queue physicalName="app.out"/>
</staticallyIncludedDestinations>
</networkConnector>
</networkConnectors>
On the application broker, there are two queues/destinations:
app.out - used by the publishing app
app.in - used by consuming app
(ISSUE) In the central broker, I am attempting to forward "app.out"
messages to "app.in"
However, the messages never get enqueued in the "app.in" in the application
broker. I can see them enquired on the "app.in" in the central broker.
Alternatively, if the "app.in" queue is on another application broker, the
forwarding works fine as expected.
Seems, there might be some config rule preventing forwarding when source
and destination are in the same broker.
How should I get around this issue?
Kunal
