Correction to version. I amusing 5.15.2
And I forgot to mention that the response code does the following:
after retrieving the command message.
message.acknowledge(); // not sure if I even need this with client ack
TextMessage reply = qSess.createTextMessage();
Hi folks,
I'm using JAVA AMQ version 5.13.2.
I have two queues for basic inter-service communications; a command queue
and a response queue
So I sent "status" over the command queue, and the java service responds
with "active".
The code in the lead service looks like this:
(maybe typos since I
Just as a personal note: in order to make an efficent use of the default
garbage collector G1, it would be a good practice to verify with your
expected typical load if
there are happening humongous allocations (
https://plumbr.io/handbook/gc-tuning-in-practice/other-examples/humongous-allocations
HI!
I can't tell what else should be needed on clustered env but:
- on the (core) client you have to add minLargeMessageSize on your URL
parameters eg tcp://localhost:61616?minLargeMessageSize=
- on the server you have to change/add journal-buffer-size on broker.xml in
order to be >=
HiHow do I change the 100KB limit of when messages are considered Large?I
have read and looked everywhere. Can it be configured both from the Client
or Server? Need to change both?I have several environments. Both singlenode
and clustered.I have Artemis 2.5.Thank you./Magnus
--
Sent from:
Thank you for your response. Regarding the cluster reconnection, I used the
setting shown in the scaledown examples:
5
I'm not sure how much effect it has on this situation though (at least in case
2), since I didn't notice anything being logged about the bridge being stopped
and JMX
