[AMQ-4742] 64-bit Java wrapper ignores wrapper.java.maxmemory values over 4096mb

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 5.5.0
• Fix Version/s: 5.10.0
• Component/s: Broker

Environment

Red Hat Enterprise Linux Server release 5.7 (Tikanga)
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
ActiveMQ 5.5.0

• Assignee: Claus Ibsen
• Reporter: Paul Lewis
• Created: 26/Sep/13 15:19
• Updated: 30/Oct/13 10:24
• Resolved: 30/Oct/13 08:43

Description

When increasing the maximum memory available to ActiveMQ via the wrapper.java.maxmemory parameter in wrapper.conf, any values above 4096mb are ignored, and ActiveMQ defaults to 4096mb. I have also tried passing in a custom 'wrapper.java.additional' parameter to set the -Xmx parameter, but this also gets ignored.

The issue is well documented at this blog: http://www.evanhoffman.com/evan/2013/08/13/java-wrapper-does-whatever-it-wants/

This is a fairly major issue at it prevents ActiveMQ scaling to memory capacities above 4GB, which in turn limits the number of messages we can effectively store on a single queue.