You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/09/30 16:04:30 UTC
[jira] [Commented] (AMQ-4742) 64-bit Java wrapper ignores
wrapper.java.maxmemory values over 4096mb
[ https://issues.apache.org/jira/browse/AMQ-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781834#comment-13781834 ]
Timothy Bish commented on AMQ-4742:
-----------------------------------
Since we are stuck using the old code from the service wrapper there's not much we can do. The Windows 64 version of the service wrapper is not available in the community edition.
> 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
>
> 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)