Excessive memory consumption in ActiveMQ broker caused by FilePendingMessageCursor instances not being released properly. This behavior leads to increased heap usage.

SELECT * FROM org.apache.activemq.broker.region.cursors.FilePendingMessageCursor -------------------------------------------------------------------------------------------------------------------------------- org.apache.activemq.usage.MemoryUsage @ 0x6c2146e50 | 80 | 958,876,920 '- listeners java.util.concurrent.CopyOnWriteArrayList @ 0x6c2146f90 | 24 | 958,875,384 '- array java.lang.Object[23834] @ 0x7085f2ef0 | 95,352 | 958,875,280 |- [13195] org.apache.activemq.broker.region.cursors.FilePendingMessageCursor @ 0x6e70df0b0| 88 | 

Although offlineDurableSubscriberTimeout is configured, messages from durable topic subscriptions accumulate in memory. Listeners in org.apache.activemq.usage.MemoryUsage retain references.