[AMQ-6940] Significant memory footprint increase from 5.8.0 to 5.15.3

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.15.3
• Fix Version/s: 5.15.4, 5.16.0
• Component/s: Broker

Environment

Java jdk1.8.0_144

OS Linux 4.4.19-29.55.amzn1.x86_64

• Flags: Important
• Assignee: Christopher L. Shannon
• Reporter: Johno Crawford
• Created: 28/Mar/18 10:21
• Updated: 30/Mar/18 16:02
• Resolved: 29/Mar/18 13:02

Description

Recently we upgraded from 5.8.0 to 5.15.3 on one of our environments and found the broker running out of memory with the old broker configurations.

I suspect this may be related to the new inflight message size calculation but haven't been able to create a reproducer just yet.

Broker JVM running with opts 

-Xss256k -Xms600m -Xmx600m -Xmn128m -Dfile.encoding=ISO-8859-1 -Dlog4j.watchDelay=60000 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+PrintPromotionFailure -XX:PrintFLSStatistics=1 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+PrintClassHistogram -verbose:gc -Dsun.rmi.dgc.client.gcInterval=7200000 -Dsun.rmi.dgc.server.gcInterval=7200000