Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Storage Manager (STM) > Properly size Java heap space in STM

Properly size Java heap space in STM

Table of contents

Updated July 12, 2017

Overview

This article describes how to properly size Java heap space in STM (STM server and STM agent).

Environment

  • STM 4.11.x 
  • STM 5.0
  • STM 5.1
  • STM 5.2
  • STM 5.3
  • STM 5.3.3
  • STM 6.0
  • STM 6.1
  • STM 6.1.1
  • STM 6.2
  • STM 6.2.1
  • STM 6.3
  • STM 6.4

Steps

There must be a 2:1 ratio of total physical RAM on the box where STM (server or agent) is installed versus the Java requirement in terms of the Java software RAM. For example, if the box has 32 GB of RAM, then Java can safely latch 16 GB of RAM. To verify this information, right-click on My Computer and check the Installed Memory (RAM) information.

 

For STM servers, the total Java RAM requirement is the cumulative value of the following services:

  • Collector
  • Event Receiver
  • Maintenance
  • Polling engine
  • Apache Tomcat
  • MySQL

To individually verify the values:

  1. Open the STM Web Console and click the left navigation pane.
  2. Click Storage Manager Health Status to display the RAM allocation for each service.

 

For STM agents, the total Java RAM requirement by default is 512 MB XMX.

To verify this information:

  1. Stop the SolarWinds Storage Manager Collector service (STM server) or the SolarWinds Storage Manager Agent service (STM agent) using services.msc.
  2. Go to C:\Program Files\SolarWinds\Storage Manager Agent\.
  3. Open the Storage Manager Agent.ini file in Notepad. 
  4. Locate the following lines and change the XMX value:
    [defines]
    EXT_ARGS=-XX:MaxPermSize=256M -Xrs -Xms67108864 -Xmx536870912 -Djsnmp.ignoreV1V2PduSizeLimit=true -Djava.net.preferIPv4Stack=true -Duser.language=en -Duser.region=US -Dsun.nio.ch.disableSystemWideOverlappingFileLockCheck=true -Dsun.lang.ClassLoader.allowArraySyntax=true -cp lib\kernel.jar com.tektools.bootstrap.BootRunner lib\core.jar

    Values with no preceding letters are calculated in byte notation such as MB and GB. The XMS value translates to the start or initialization value of Java. The XMX Java heap size translates to the maximum or end value that Java increases to once it starts getting into full stride. For example, if the box has a total of 8 GB RAM and serves only as an STM Java agent, you can increase the XMX value accordingly.
    In this example, change the XMX value to 4096M or 4 GB of RAM.
    The following is the result of the change:
    [defines]
    EXT_ARGS=-XX:MaxPermSize=256M -Xrs -Xms67108864 -Xmx4096m -Djsnmp.ignoreV1V2PduSizeLimit=true -Djava.net.preferIPv4Stack=true -Duser.language=en -Duser.region=US -Dsun.nio.ch.disableSystemWideOverlappingFileLockCheck=true -Dsun.lang.ClassLoader.allowArraySyntax=true -cp lib\kernel.jar com.tektools.bootstrap.BootRunner lib\core.jar
  5. Save the Storage Manager Agent.ini file.
  6. Restart the service.

 

Last modified

Tags

Classifications

Public