[AMQ-3392] Doc change to http://activemq.apache.org/javalangoutofmemory.html

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 5.6.0
• Component/s: Documentation
• Labels: documentation
• Patch Info: Patch Available
• Assignee: Gary Tully
• Reporter: James Green
• Created: 04/Jul/11 15:57
• Updated: 20/Sep/11 10:42
• Resolved: 04/Jul/11 16:19

Description

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.

Issue Links

• duplicates: AMQ-2819 javax.management.InstanceAlreadyExistsException when registrating an MBean