On 9/17/24 05:15, Devriendt, Erik wrote:
Hello Ken
Your link points to the documentation of the ActiveMQ Classic version.
Patrick indicates as version: AMQ: v2.36.0, which is the Artemis version.
I think a better link is
https://activemq.apache.org/components/artemis/documentation/latest/federation.html#federation
Anyhow, several months ago (February 2024) I had a similar federation question
for this mailinglist.
The title was ' Is a federation of Hub-spoke broker topology possible with
Artemis?'. I guess it can be found in the archives of this list.
Unfortunately the list members were not able to help me. In addition, I got
higher prio tasks to execute and so I did not investigate my problem any
further.
I am curious if someone gets this transitive broker federation to work this
time.
There is a hub and spoke example for configuring AMQP broker federation
for multicast addresses
https://github.com/apache/activemq-artemis-examples/tree/main/examples/features/broker-connection/amqp-federation-multicast-hub-spoke
Kind regards
Erik Devriendt
-----Original Message-----
From: Ken Liao <kenlia...@gmail.com>
Sent: Tuesday, 17 September 2024 02:35
To: users@activemq.apache.org
Cc: Justin Bertram <jbert...@apache.org>
Subject: Re: ActiveMQ Federation Questions
Hi Patrick
https://activemq.apache.org/components/classic/documentation/networks-of-brokers
In the documentation, there's a configuration for messageTTL in
NetworkConnector and the default is 1. I have not verified the documentation
myself or have ever used MQTT, so there's a chance that it's outdated or it's
not the fix for the issue that you are encountering.
Thanks,
Ken
On Mon, Sep 16, 2024 at 9:41 AM Patrick Apichart <
kittipat.apicharttris...@gmail.com> wrote:
Thank you Justin for your reply and invitation on Slack.
Because you mentioned a larger audience on this mailing list, let me
describe my issue here.
I am configuring AMQ to form a simple fanout federation like (top
broker)
--> (middle broker) --> (bottom broker), where an arrow represents
--> upstream
to downstream relationship. According to the AMQ document, I only
configured a downstream broker to connect to an upstream broker using
a simple static connector and forward-all "#" address for federation.
However, when I connect an MQTT publisher to the top broker and an
MQTT subscriber to the bottom one, the latter cannot receive the sent message.
When I instead connect the subscriber to the middle broker, it can
receive the message, and the same applies when I connect publisher to
middle and subscriber to bottom. In other words, the federation only
works when brokers are "one hop" away and does not work when they are further
apart.
AMQ documents do not provide details on how to configure fanout
topology except to set max-hops, and all the activemq federation
examples are basically "one-hop-away" type. Therefore, may I ask the
community how I can make fanout federation works, and even better may
I have an example broker.xml for a fanout?
Below are basic setups on my side.
OS: Ubuntu 22.04
AMQ: v2.36.0
Thank you,
Patrick
On Mon, Sep 16, 2024 at 11:45 AM Justin Bertram <jbert...@apache.org>
wrote:
This mailing list is the right place to ask questions about all
things ActiveMQ.
The Slack channel is currently active. I've sent you an invitation.
Feel free to elaborate on your issue here or on Slack, although the
audience will be much larger here on the mailing list than on Slack.
Justin
On Mon, Sep 16, 2024 at 10:26 AM Patrick Apichart <
kittipat.apicharttris...@gmail.com> wrote:
Dear Community,
I am a new member and unsure where to send questions regarding AMQ.
Also, I
am wondering if the Slack channel is currently active and if
anyone may kindly invite me to the channel. I am currently having
an issue with
AMQ
federation configuration for fanout topology and need insightful
assistance
from the community.
Thank you,
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
For additional commands, e-mail: users-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
--
Tim Bish
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
For additional commands, e-mail: users-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
