OK, no subscriber on the proxy broker certainly explains why no messages are making it to the main broker, so let's dig into that.
Do you see (via JMX) a networkConnector between the two brokers? And do you see advisory messages passing from the main broker to the proxy when a subscriber connects? With dynamically included destinations, if the advisory messages aren't flowing, you're not going to get any inter-broker subscriptions established. Also, I'd suggest that you set up the main broker as a standalone broker instance. This is how you're going to run eventually anyway, and you'll have an easier time troubleshooting problems if you have access to log files, simpler JMX configuration, etc., which may make it easier to work through whatever's going wrong now. BTW, I may have led you down the wrong path on the mechanism for including destinations, because I forgot a very important advantage that statically included destinations have over dynamically included ones: messages will be forwarded to the main broker even when there are no consumers attached to the main broker. Of course, this advantage only really matters for queues, because for topics a message will be discarded if there are no subscribers, and so all you're changing is where the message gets discarded. But if you plan to have queues in addition to the topic shown in your example, this might make a difference to you. But if you're going to be topic-only, then there's no disadvantage to using dynamically included destinations per your current setup. Tim On Mon, Jul 31, 2017 at 8:28 AM, Mark Raynsford < list+org.apache.activ...@io7m.com> wrote: > Still no luck, unfortunately. This is the test program I'm using now: > > http://ataxia.io7m.com/2017/07/31/ForwardingServers.java > > I use setDynamicallyIncludedDestinations() with a wildcard topic ">". I > still see no subscriptions on the proxy broker from the receiver broker. > > -- > Mark Raynsford | http://www.io7m.com >
