Hi Paul-
Message flow and cluster troubleshooting is generally beyond what is feasible
to support via mailing list.
Check out ActiveMQ support options, or try to jump into the #activemq Slack
channel (I sent you an invite).
Thanks,
Matt Pavlovich
> On Sep 29, 2023, at 7:41 AM, Paul Burgess w
I Agree and added a note on that regards to
http://activemq.apache.org/networks-of-brokers.html.
Give it an hour or two for the change to be uploaded.
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Nov 9, 2011, at 6:07 PM, James Green wrote:
> This availability should be express
This availability should be expressed on
http://activemq.apache.org/networks-of-brokers.html
As it stands only tcp:// is given (that I can see). Nothing suggests
anything other than tcp can be used.
James
On 9 November 2011 16:36, Dejan Bosanac wrote:
> Yes,
>
>
> https://fisheye6.atlassian.co
Yes,
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-optional/src/test/java/org/apache/activemq/bugs/AMQ2764Test.java?hb=true
tests network connectors over http scenario. Of course, you should test
your use case.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
---
Just to be clear, we could ship software containing an embedded or
standalone broker that is told to connect to (for argument's sake)
https://broker1.mycompany.com:61616 and
https://broker2.mycompany.com:61616and it will form part of the broker
network allowing clients to connect
locally?
James
O
You can use http transport inside you network connector, no problem about
that.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www
