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

["Paul Lewis (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808889#comment-13808889 ] 

Paul Lewis commented on AMQ-4742:
---------------------------------

Hi Claus,

The original issue I raised was that we couldn't address more than 4GB of memory when using the 64-bit Linux wrapper, so at the very least, it would be worth putting the same note about the memory limit under the Linux wrapper section of the page you updated.

However, I guess I'm more interested in whether this will ever be fixed, or whether we will have to look at other queues in order to be able to address more than 4GB memory?

Thanks,

Paul

> 64-bit Java wrapper ignores wrapper.java.maxmemory values over 4096mb
> ---------------------------------------------------------------------
>
>                 Key: AMQ-4742
>                 URL: https://issues.apache.org/jira/browse/AMQ-4742
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>         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
>            Reporter: Paul Lewis
>            Assignee: Claus Ibsen
>             Fix For: 5.10.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1#6144)