Yes, the buffer was changed to a direct byte buffer for performance reasons. This was done in https://issues.apache.org/jira/browse/AMQ-6184
I think the best thing you can do for now is to keep increasing the size and see if it stabilizes. You mentioned that you could see it using 10g under version 5.10 so maybe you can set it to that and see if it will run without running out of memory. My guess is your app just needs that much memory to run and there isn't an actual memory leak going on but hard to say until you increase the available memory to the same amount 5.10.2 uses. On Tue, Jun 7, 2016 at 10:11 PM, RuralHunter <ruralhun...@gmail.com> wrote: > I found this article: http://www.evanjones.ca/java-bytebuffer-leak.html > I guess 5.10.2 uses 'Heap ByteBuffers' which is backed with unlimited > 'temporary Direct ByteBuffer', while 5.13.3 uses 'Direct ByteBuffer' > directly? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/nio-buffer-memory-problem-tp4712706p4712766.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
