JMS (ActiveMQ) heap memory exception - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

JMS (ActiveMQ) heap memory exception - Connect IT Community | Kaseya

PROBLEM

The Internal Communication Bus (aka JMS) component terminates with a heap memory exception.

CAUSE

Typically occurs when Traverse grows to more than 25 servers (BVE, DGEs, extensions).

RESOLUTION

Do not implement the following changes unless instructed to do so via a ticket by Kaseya Support. These changes apply only to the 'Internal Communication Bus' component (a.k.a. JMS) on the BVE.

'TRAVERSE_HOME' should be replaced by the actual Traverse installation location in the paths below.

To increase the heap memory utilized by JMS/ActiveMQ on a Linux BVE:

Install the 64bit Java 1.6 (Java 6 is a requirement) on the Traverse BVE, if not already present:

yum install java-1.6.0-openjdk

Stop all Traverse BVE components

cd TRAVERSE_HOME/etc ./traverse.init stop

Modify 'TRAVERSE_HOME/etc/jms.init' to use the 64bit Java Virtual Machine, instead of the 32bit version included with Traverse. For example if the 64bit Java is installed under '/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.34.x86_64/jre', then insert this line above 'JAVACMD=' in order to utilize the 64bit JVM:

JAVA_HOME="/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.34.x86_64/jre"

In the same file, increase the maximum heap memory allocated from '512m' to '1536m' :

## Increase max memory to 1536

JAVACMD="${JAVA_HOME}/bin/java -Xmx1536m -Xss256k -Djava.ext.dirs=${JAVALIB}"

Start the JMS component and ensure that it remains running:

./jms.init start

Then start the remaining Traverse components:

./traverse.init start<br>

To increase the heap memory utilized by JMS/ActiveMQ on a Windows BVE:

Install the 64bit Java 1.6 JRE from the Oracle web site (Java 6 is a requirement) on the Traverse BVE, if not already present
Stop all Traverse BVE components via the Traverse Service Controller
Modify 'TRAVERSE_HOME\bin\jms.lax' to use the 64bit Java instead of the 32bit version included with Traverse. For example, if the 64bit Java binary is installed under 'C:\Program Files\Java\jre6', then change this line to reference the 64bit JVM:

lax.nl.current.vm=C:\\Program Files\\Java\\jre6\\bin\\java.exe<br>
Also increase the maximum heap memory allocated from '512m' to '1536m' :

lax.nl.java.option.additional=-Xmx1536m -Xss256k ....
Start only the 'Internal Communication Bus' component using the 'Traverse Service Controller' and ensure that this component remains running
Start the remaining Traverse components via 'Traverse Service Controller'

APPLIES TO

All versions of Traverse.

REFERENCE

None.