If you could produce just a simple, single, self contained JUNit test or java main class that does something like:
1) Send some messages with filters
2) Consume them
Then we can inspect whether there is anything left in memory at the end.
Honestly, we're not trying to be awkward here, it's just we have such limited resources, and we have to deal with a lot of enquiries and issue reports and simply don't have the time to import/learn X number of tools.
If there is really an issue here (and I don't doubt there might be), it should be simple to reproduce in a basic test case
Hi Tim,
I have found the problem, it was in my configuration after all! The following configuration was causing the issue:
Glad to hear it
BTW... if you want the highest throughput using 2.1.0, there are some new settings - take a look at the performance section in the user manual.
2.1.0 Also comes pre-configured with a new ThroughputConnectionFactory which has these settings set