I agree with Gary that it's not reasonable to expect to view the entire
"large" message in the web console. Large message support is intentionally
designed to handle the message in chunks so that the whole message is never
in memory at once. This avoids excessive memory utilization that would
other
Hi Magnus,
I recently limited the amount of data that is returned via
JMX/management, with a default of 256 bytes[1].
For large messages, the body should be a string "large message",
ensuring that just to browse large messages does not require us to
load the message body into memory on the broker o
We have upgraded our Apache Artemis broker from version 2.10.1 to latest
2.17.0 in order to get improved management console functionality (provided
by hawtio 2).
We were especially hoping that the upgraded console could show the message
content for large messages.
Both AMQP (.NET clients) and a
