Hi
It worked as a charm. Many thanks.
To have it working in a Cluster Env you also need to change
min-large-message-size in in Broker.xml to same or
above.
@jbertram:
What is the "limit" message size for AMQP?
Thank you
/Magnus
--
Sent from:
AMQP messages arent classed as being 'large' or not at a protocol
level, but rather just messages which can be sent using 1 or more
message-transfer frames as needed or appropriate to the situation.
Messages can be split into multiple frames based on the servers
advertised max frame size, which it
> But I don't understand why a client should decide on how a message should
be treated on the server.
Because "large" message support as originally conceived for the "core"
protocol (the foundational protocol used by Artemis) involves (at least in
part) clients *streaming* messages in chunks to
Hi
Thanks for your answer.
I find the answer a bit strange. It probably is correct though.
But I don't understand why a client should decide on how a message should be
treated on the server. As in my case the client can actually crash my
consumer (As it cannot read large messages if put in
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:
