[
https://issues.apache.org/jira/browse/AMQ-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3392.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Gary Tully
updated. thanks.
> Doc change to http://activemq.apache.org/javalangoutofmemory.html
> -----------------------------------------------------------------
>
> Key: AMQ-3392
> URL: https://issues.apache.org/jira/browse/AMQ-3392
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Documentation
> Reporter: James Green
> Assignee: Gary Tully
> Priority: Trivial
> Labels: documentation
> Fix For: 5.6.0
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> The bullet points could I think be clearer:
> -Xmx: If your OS has more available memory, consider increasing the total
> heap memory available to the broker JVM. Note that the JVM will require more
> memory than the -Xmx value. Thread stacks and the JMVs internal classes will
> consume additional memory.
> -Xss: If you have massive numbers of threads in the Broker JVM, consider
> reducing the default JVM stack size of each thread with the -Xss option.
> By default, the ActiveMQ startup scripts start the JVM with 512mb of
> memory.
> If you are running an embedded broker or in a third party container,
> ensure that the hosting JVM has appropriate values for the maximum heap and
> stack sizes.
> The line "By default...." onwards should not be part of the -Xss bullet point
> as it leads to implied referencing by the reader.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
