Search code examples
jmsactivemq-classiccluster-computingbroker

Does activemq static network of broker stop forwarding messages without advisorySupport enabled?

I have set up a network of brokers exactly as per this post of Bruce Snyder:

Broker 1:

<networkConnector name="amq1-nc"
uri="static:(tcp://localhost:61617)"
userName="system"
password="manager"
/>

Broker 2:

<networkConnector name="amq2-nc"
uri="static:(tcp://localhost:61616)"
userName="system"
password="manager"
/>

I have advisorySupport="false" in the broker tag of both the broker's config XML and started both the brokers.

Then I started the consumer using the command:

ant consumer -Durl=tcp://0.0.0.0:61616

and finally started producer using this command:

ant producer -Durl=tcp://0.0.0.0:61617

All the produced messaged then go in the pending state on the broker running on port 61617 and consumer connected on port 61616 broker never gets the messages.

Does the network of brokers stop forwarding messages without advisorySupport enabled? I thought that was fixed in a recent release. (I'm using activemq 5.4.2 release).

Does ActiveMQ static network of brokers stop forwarding messages advisorySupport is disabled?

Update: I ran into issues using advisorySupport="false" and staticallyIncludedDestinations.

We use JMS for mostly request-response like described here: http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html

We are using a temporary queue on the Producer side to be able to receive response from Consumers and since staticallyIncludedDestinations cannot include these temporary queue names in it, therefore, all the Producers are unable to receive responses back from clients when advisorySupport is disabled.

I am coming to the conclusion that for our scenario advisorySupport cannot be turned off unless there is some other config trick I'm not aware of.

Solution

  • The documentation sais:

    "Warning: Advisory messages are required for dynamic network broker topologies as NetworkConnectors subscribe to advisory messages. In the absence of advisories, a network must be statically configured.

    The Advisory messages tell a node where remote consumers are and therefore where to send incoming messages. WITHOUT them, you have to configure that stuff yourself.

    The documentation has an example how to do that: http://activemq.apache.org/networks-of-brokers.html