[
https://issues.apache.org/jira/browse/AMQ-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015879#comment-13015879
]
Dejan Bosanac commented on AMQ-3269:
------------------------------------
One more fix available in svn revision 1088989
After a closer look (thanks Gary) the problem is that ACTIVEMQ_OPTS were set
before we loaded config files. That's fixed now.
> ACTIVEMQ_OPTS_MEMORY is ignored
> -------------------------------
>
> Key: AMQ-3269
> URL: https://issues.apache.org/jira/browse/AMQ-3269
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.0
> Reporter: James Green
> Assignee: Dejan Bosanac
> Priority: Minor
> Fix For: 5.6.0
>
>
> I have just realised that my brokers were running with 256M of ram, which
> given they used to operate on 512M raised concerns. Checking my
> /etc/default/activemq file I do have:
> ACTIVEMQ_OPTS_MEMORY="-Xms512M -Xmx512M"
> If I echo out the result of ACTIVEMQ_OPTS within the init.d script (linked to
> /opt/activemq/bin/activemq) I see only the default 256M resolved.
> Only way I was able to up the limit was by editing the init script and
> replacing the default value with my own.
> Marking this as a regression as I am 99% sure this was working in 5.4.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
