Inter broker communication clustering, federation and bridges all work only
using the brokers native core protocol.Sent from my Samsung Galaxy smartphone.
Original message From: BBruhn
Date: 01/06/2020 19:21 (GMT+00:00) To: users@activemq.apache.org Subject:
Alternative to Co
Hello,
Our application has to run under strict firewall policies.
An Artemis Broker behind a firewall should communicate with an Artemis
Broker in a Cloud Environment.
Preferably, the communication between brokers only uses MQTT over
Websockets.
I tried using Address Federation in this scenario
Does disabling one but not both of those things also fix the problem? Or is
the problem only eliminated if both are disabled?
Tim
On Mon, Jun 1, 2020, 7:44 AM sainath
wrote:
> Hi All,
>
> We disabled JMX and advisories, this seems to fix the memory issue.
>
> In the ActiveMQ.xml file we
>
> Add
Hi All,
We disabled JMX and advisories, this seems to fix the memory issue.
In the ActiveMQ.xml file we
Added these flags useJmx="false" and advisorySupport="false"
eg:
http://activemq.apache.org/schema/core";
brokerName="localhost" dataDirectory="${activemq.data}" useJmx="false"
advisor
