Publishers can't enqueue messages locally without a broker. No broker, no
work done.
However, it's possible to embed a broker within the producer process, which
would then connect to the external broker when available and buffer
messages when the connection is broken. But this adds complexity
Hi,
We have a setup Artemis broker sits behind SSL offloading hardware.
client ---TLS---> VIP(ssl-offload) ---TCP--> Artemis broker
We have a HA setup with one master and one broker. I have followed the
examples and add two TransportConfigurations one for each.
ActiveMQConnectionFactory
On Fri, May 13, 2016 at 9:44 AM, siddutta wrote:
> I wish to run an experiment in which the publisher loses connection with
> the
> broker and then enqueues them in its own queue and then when it regains
> connectivity it send s all its queued messages to the broker.
I have a use case where i have to get the broker service instance for the
remote broker or getting the remote broker instance. I have tried in
creating broker service instance and adding the remote connector uri address
but thats not helping me to get the region broker and i am in need of region
Hi,
I am trying to run transaction failover test which is present below on my
local server cluster
https://github.com/apache/activemq-artemis/blob/master/examples/features/ha/transaction-failover/src/main/java/org/apache/activemq/artemis/jms/example/TransactionFailoverExample.java
As I read
Hi,
I am trying to restrict SASL mechanisms. I could not find how to do it in
documentation. Is it possible to restrict SASL mechanisms for instance to
EXTERNAL only?
Vavricka
--
View this message in context: