Can't read the last message on the queue while using Apache ActiveMQ Artemis 2.16.0

[piroMe]

Specifications

• JMSToolBox version:
• Windows 10 (64bits):
• Q provider (Apache ActiveMQ Artemis, 2.16.0) :

Expected Behavior

Throws no error while attempting to read the last message on the queue

Actual Behavior

Throws an error

org.eclipse.e4.core.di.InjectionException: java.lang.RuntimeException: AMQ219023: The large message lost connection with its session, either because of a rollback or a closed session
java.lang.RuntimeException: AMQ219023: The large message lost connection with its session, either because of a rollback or a closed session

and on a second attempt to open a message writes null, null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,

However,

To open an actual message I have to send two messages to the queue and open only the previous, but not the last
message

Steps to Reproduce the Problem

1. create a message (Type: Bytes)
2. import a payload of type of zip
3. send a message to the queue
4. try to view the message

Logs

Eventually, attach the log files which are "<user>\.jtb\JMSToolBox\jmstoolbox.log [JTB_20205529_2311657_jmstoolbox.log](https://github.com/jmstoolbox/jmstoolbox/files/5634770/JTB_20205529_2311657_jmstoolbox.log) " and "<user>\.jtb\.metadata\.log"
They can be exported directly from JMStoolBox: Menu "Help" > "Export JMSToolBox log files..."
JTB_20205529_2311657_jmstoolbox.log

[titou10titou10]

The logs updated does not contain the stack trace
Q: do you have other program than JTB that can read the messages?
Q: what is the size of your messages?
It seems you are in this situation: https://stackoverflow.com/questions/59651341/polling-byte-large-messages-from-activemq-artemis-using-apache-camel-consumert
Could you try to add?minLargeMessageSize=<some large value ie 512MiB or more>to your brokerURL?
Ref: https://activemq.apache.org/components/artemis/documentation/latest/large-messages.html

[piroMe]

Thank you for your response.

do you have other program than JTB that can read the messages?

No.

what is the size of your messages?

varies in size [3kb to 1GB]

Could you try to add?minLargeMessageSize=<some large value ie 512MiB or more>to your brokerURL

how this could help?

[titou10titou10]

how this could help?

• The answer is in the second link of my previous post that. Did you read it?
• Did you try it, ie set minLargeMessageSize with a value bigger that your biggest message?

"Large message" is a very specific proprietary "feature" in ActiveMQ and Artemis . Client has to be aware of large message and process them differently wich is not the vocation of a tool like JTB that is a generic JMS tool. Setting this parameter will make the message not be considered as "large"

[piroMe]

yes I've read it and applied your proposed solution, but it did not work.
Now, no new messages show up on jmstoolbox

[titou10titou10]

what string do you use forbrokerURLnow?

[piroMe]

tcp://localhost:61616?minLargeMessageSize=5368709120