Looks like this was a dead end. I found the reason I needed to start the
connectors was because I added them after the broker was already running. I
guess if you add them before you start the broker then you don't need to
start them explicitly...
Tomas
--
View this message in context:
http://a
'Ello.
On 2017-08-02T00:19:48 -0700
tpavelka wrote:
> I know nothing about static destinations but one thing I noticed in your
> Github code: when you add network and transport connectors, you do not start
> them. I tested this with one of my sample ActiveMQ programs and if I don't
> start the c
I know nothing about static destinations but one thing I noticed in your
Github code: when you add network and transport connectors, you do not start
them. I tested this with one of my sample ActiveMQ programs and if I don't
start the connectors then there are no messages flowing.
Try to use:
org
'Ello.
For the purposes of keeping everything consistent, I've pushed my
example program to a GitHub repository:
https://github.com/io7m/activemq-examples
See:
https://github.com/io7m/activemq-examples/blob/develop/src/main/java/com/io7m/activemq/examples/ForwardingServers.java
I've also
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?
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 | h
On 2017-07-31T06:55:07 -0600
Tim Bain wrote:
> People do what you're trying to do, so this is a use case that works (or at
> least, did work at some point in the past).
Right.
> My advice when message forwarding isn't working in a network of brokers is
> to use JMX to figure out what's going on
People do what you're trying to do, so this is a use case that works (or at
least, did work at some point in the past).
My advice when message forwarding isn't working in a network of brokers is
to use JMX to figure out what's going on in each broker. I'd start with the
proxy broker and confirm th
Hm, is anyone out there actually using ActiveMQ in this manner?
The reason I'm doing this is that I'm considering deploying message
brokers in a manner analogous to the way in which one would
typically deploy mail servers: Programs on a server communicate with an
MTA (such as Postfix or qmail) on
Slightly shorter and simpler example here:
http://ataxia.io7m.com/2017/07/30/ForwardingServers.java
I've tried to step through the broker code in a debugger, but I'm not
familiar with the ActiveMQ sources, and regardless it's pretty tough to
use a debugger to find problems of the class "nothing
On 2017-07-29T18:57:30 -0600
Tim Bain wrote:
> If you use the TCP transport for the networkConnector between the brokers,
> does it work? I've got a half-memory of a mailing list post where someone
> found that the NIO transport didn't work in a networkConnector, but I can't
> find it now so it's
If you use the TCP transport for the networkConnector between the brokers,
does it work? I've got a half-memory of a mailing list post where someone
found that the NIO transport didn't work in a networkConnector, but I can't
find it now so it's possible I'm misremembering.
Tim
On Jul 29, 2017 2:0
12 matches
Mail list logo
