Memory leak after sending ByteMesssage to AMQ

[geertschuring]

Specifications

• JMSToolBox version: 6.2.0
• OS (Name, version, 32/64bits): Windows 64bits
• Q provider (kind, version) : Apache Artemis MQ Artemis v2.x

Expected Behavior

Send a large file and clear the contents from the local memory afterwards.

Actual Behavior

The file is send, but the memory is not cleared, it remains on the heap of JMSToolbox even after closing the connection to the broker.

Steps to Reproduce the Problem

1. Send a new message to a Queue with Payload Type: Bytes and of significant size (like 200MB)
2. Observe the heap of JMSToolbox, trigger a GC and notice the memory it not released.
3. Repeat above steps until JMSToolbox crashed with out of memory errors.

[titou10titou10]

Not sure it's a bug, but mostly inherent to the way JTB is working
There is no "lazy loading" of messages, so if you have 200 messages in the message browser, those 200 messages are all "loaded" in JTB memory

You can adjust the memory used by JTB by editing the JMSToolBox.ini file in the installation directory by changing the "-Xms"and "-Xmx" parameters
There is no maximum set by default, so JTB will use half of the RAM of your machine on Windows for example

{...} it remains on the heap of JMSToolbox even after closing the connection to the broker.

The heap does not go down after a while after closing the connection?

2. Observe the heap of JMSToolbox, trigger a GC and notice the memory it not released.

How do you trigger a GC?