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 otherwise be required when dealing with such large messages.
Justin On Wed, Apr 28, 2021 at 8:10 AM Magnus Johansson <[email protected]> wrote: > 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 an Apache Camel bridge publishes messages to > the broker. We are running Artemis on Windows. > > Artemis 2.10.1 > ============ > > In version 2.10.1, all messages labeled as "large" and stored in the > data\large-messages folder cannot be displayed, using a test message/file > that has the size 1.5 MB: > > "Unsupported message body type which cannot be displayed by hawtio" > > I have been using default values for minLargeMessageSize on the acceptors > and Camel Connection factory: > > Artemis 2.17.0 > ============ > > The same 1.5 MB message sent via AMQP shows some inconsistent behavior. > > Acceptor: > > <acceptor > name="artemis">tcp:// > 0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBuffe > > rSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP;useEpoll=tr > <http://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP;useEpoll=tr> > > ue;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true</acceptor > > > > The large message content can be displayed in the console. > > However the column Large = false for this message even if it is much larger > than 102400 bytes. > > But the message is stored under the folder data\large-messages. So here is > the inconsistency, the message is large, but since Large=false, the content > can be displayed in the console (which is what I want). > > If the same 1.5 MB content is pasted into "Send Message" in the console, > Large=true and the content cannot be displayed, it just says "(large > message)" > > > > Also if the message is received via the Apache Camel bridge, we get the > same > behaviour. Large=true and the content cannot be displayed. That is a > problem > for us! > > To sum it up > ========== > > How can I display message content for "large messages" to some extent? I > understand that the console cannot show infinitely large messages, but > maybe > up to some limit where it truncates. > > Best regards > > Magnus Johansson > CMJ Solutions AB > > >
