[QPIDJMS-543] Memory usage has increased significantly because the PooledByteBuffer(netty) are not released

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Feedback Received
• Affects Version/s: 0.56.0
• Component/s: qpid-jms-client
• Labels: memory-analysis memory-bug memory-dump memory-leak memorymanager

Environment

java - 11

qpid-jms-client - 0.56.0

netty - 4.1.65.Final

• External issue URL: https://github.com/netty/netty/issues/9768
• Assignee: Unassigned
• Reporter: Rishabh Handa
• Created: 14/Jul/21 04:41
• Updated: 21/Jul/21 07:51
• Resolved: 21/Jul/21 07:51

Description

• We are using JMS to send and receive messages from queue asynchronously
• We have observed a high heap memory usage by io.netty.buffer.PoolChunk - (heap dump: screenshot attached 1)
• These PoolChunks are allocated during creation of a connection to the queue - 
  • From stacktrace(screenshot attached 2) - when we invoke jmsConnectionFactory.createConnection()
    internally the call goes to FailoverProvider -> AmqpProvider, which invokes ByteBufferUtil to create PooledByteBuffer
  • These buffers are created on the heap memory (io.netty.buffer.PoolChunk of 16 MB)
• These PooledByteBuffer are not released from the heap memory even after the connection is closed. Due to which, the memory usage has increased.

 

For more details - please go through this issue: Increased memory footprint in 4.1.43.Final · Issue #9768 · netty/netty (github.com)