-The above policy will instruct ActiveMQ to remove dead queues after 5 minutes.
-
-### Optimize network usage for direct requests in a network of brokers
-If you are using a network of brokers you will need to make a big change to how that works.
-At present we tend to have 1 bi-directional connection for everything, with direct requests
-we dedicate a bi-directional connection for these queues leaving the other just for topics.
-
-{% highlight xml %}
-<networkConnectors>
- <networkConnector
- name="stomp1-stomp2-topics"
- uri="static:(tcp://stomp2.xx.net:6166)"
- userName="amq"
- password="secret"
- duplex="true"
- decreaseNetworkConsumerPriority="true"
- networkTTL="2"
- dynamicOnly="true">
- <excludedDestinations>
- <queue physicalName=">" />
- </excludedDestinations>
- </networkConnector>
- <networkConnector
- name="stomp1-stomp2-queues"
- uri="static:(tcp://stomp2.xx.net:6166)"
- userName="amq"
- password="secret"
- duplex="true"
- decreaseNetworkConsumerPriority="true"
- networkTTL="2"
- dynamicOnly="true"
- conduitSubscriptions="false">
- <excludedDestinations>
- <topic physicalName=">" />
- </excludedDestinations>
- </networkConnector>
-</networkConnectors>
-{% endhighlight %}
+See [the ActiveMQ config reference][activemq_config] for details on configuring ActiveMQ for this connector. As recommended at the top of the reference, you should skim the sections you care about and edit an example config file while reading.