When I have configuration like "", does it mean each queues will
take up to total of 1 MB of messages before it starts blocking producer
messages?
Thanks
Regards,
Rahman
Thank you for the detailed explanation. The part about datastore locking and
how brokers behave is more or less clear.
So would you recommend using randomize=false? We will have moments where slave
becomes master and stays that way for extensive period of time. Does this mean
that with randomiz
Hi,
masterslave: transport is deprecated. You can achieve the same with
randomize=false basically.
Correct: updateClusterClientOnRemove is only for network connection, but
when you have active/active (so a real network).
No, the clients won't be stuck: they will reconnect to the new master.
Hello,
>From ActiveMQ 5.15.9, the exception is raised as a warning and doesn't prevent
>the send of the message:
2021-11-22 16:02:52,432 | WARN | handleException /admin/message.jsp
java.io.UTFDataFormatException | org.eclipse.jetty.server.HttpChannel |
qtp1099552523-44
>From Artemis 2.16, t
can you post some code and/or the exception stack trace?
On Tue, 30 Nov 2021 at 08:46, BRASSEUR Pierre-Henry
wrote:
>
>
> Hello,
>
> I would like to know if Artemis can support other charset than UTF-8?
>
> The post of message in charset ISO-8859-15 was working with previous version
> ActiveMQ 5
Hello,
I would like to know if Artemis can support other charset than UTF-8?
The post of message in charset ISO-8859-15 was working with previous version
ActiveMQ 5.15.9.
We upgraded to Artemis 2.16 and messages with special characters are now
rejected by Artemis (exception on
org.apache.acti
Thank you for your response!
Just out of curiosity, what is this masterslave:() transport is about then?
Also, if I don't configure network connection will
updateClusterClientsOnRemove parameter take effect?
My main concern is that clients will go into stuck state during/after the
failover. I
