activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Network of Brokers with load balancing
Date Tue, 24 May 2016 12:23:00 GMT
Nothing about your setup seems obviously wrong.  Enabling JMX and using a
JMX viewer such as JConsole is typically the best way to troubleshoot
issues like these.  First just check that a connection exists between B1
and B3.  Then see if the subscription from B3 to B1 (or vice versa) exists
on the queue.  Finally publish a message and see where it gets dispatched
(which broker, and which consumer) or whether it sits on the broker to
which it was published.  Through it all, make sure there are no errors,
warnings, or unexpected info lines in any of the logs.

Also, I assume you're either only connecting one consumer at a time to your
test queue or publishing at least as many messages as you have consumers,
otherwise your test is invalid/inconclusive.

Tim
On May 18, 2016 7:18 AM, "issacjohn81" <issac.john@gadgeon.com> wrote:

> Hi,
>
> I have 3 brokers. Let say B1, B2 and B3.
>
> B1 has a network connector configuration as shown below:
>
>         *<networkConnectors>
>                  <networkConnector name="MQTTNC"
>
> uri="static:(tcp://B2server:61616,tcp://B3server:61616)"
>                         dynamicOnly="true"
>                         networkTTL="3"
>                         duplex="true" />
>         </networkConnectors>
>         <transportConnectors>
>
>             <transportConnector name="openwire"
> uri="tcp://
> 0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600
> "/>
>             <transportConnector name="amqp"
> uri="amqp://
> 0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600
> "/>
>             <transportConnector name="stomp"
> uri="stomp://
> 0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600
> "/>
>             <transportConnector name="mqtt"
> uri="mqtt://
> 0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600
> "/>
>             <transportConnector name="ws"
> uri="ws://
> 0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600
> "/>
>         </transportConnectors>
>
>
> *
>
> The connection is duplex in nature from B1 to B2 as well as from B1 to B3.
> I
> am able to publish messages (using mosquitto publish command) from B2 to a
> subscriber connected to B1. Similarly a subscriber connected to B2 is able
> to receive messages published from B1 (using mosquitto publish command).
> But
> at the same time, i am not able to do the same between B1 and B3.
>
> I would like to a have network where in messages sent from outside (towards
> B1) should be load balanced between B2 and B3 subscribers (without any
> duplication ), and also messages published from B2 or B3 should be sent to
> the outside world subscribers (subscribed to B1).
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Network-of-Brokers-with-load-balancing-tp4712096.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message