SOI Tech Tip - Increase Manager Memory to accomodate more Connectors.

Document created by Jerald_Holcomb Employee on Jul 6, 2014
Version 1Show Document
  • View in full screen mode

SOI 3.2

 

Make sure you have enough resources on the SOI Manager in large connector deployments..

 

The sizing of the CA SOI installation depends on the number of CIs (Configuration Items).

 

There is no dedicated CA SOI sizing documentation. You can  the SOI Implementation Guide

for diagrams of each configuration.

 

 

To Increase Memory Heap on the SOI manager:

Add  ram to the SOI 3.2 Manager Virtual or Physical.

 

Open SOI Manager Debug page

http://SOImanager:7090/sam/debug

Sample Table showing heap usage. If Free MB is low add Memory.

  Pool Name   Total 
MB
  Init 
MB
  Free 
MB
  Limit 
MB
  Used 
MB
  Usage 
%
Heap9901,0244933,96049712.5
Perm Gen14621025014658.4
Code Cache1420481429.7
Eden Space273273211,09225323.1
Non-Heap16123029816053.8
Survivor Space34343313610.7
Tenured Gen6836834402,7312438.9

 

Edit the  jsw\conf\wrapper-jvm-64.conf file and change the setting for

JAVA_MAXMEM_MB depending on how much ram you have available.

 

 

============

#encoding=UTF-8
#
# Configuration settings for running as 64-bit service

# JRE directory (JAVA_HOME)
set.JAVA_HOME=C:\Program Files (x86)\CA\SOI/jre-64

# When WSO2 registry is run, we'll get OutOfMemory for PermGen unless increased - wrapper.java.additional.#=-XX:MaxPermSize
set.JAVA_MAX_PERM_SIZE=250m

# Initial Java Heap Size (in MB) - wrapper.java.initmemory
set.JAVA_INITMEM_MB=1024

# Maximum Java Heap Size (in MB) - wrapper.java.maxmemory
set.JAVA_MAXMEM_MB=4096

 

 

Set this setting to the amount of memory you require.
Restart the manager and check the heap from the debug page.

You will now have more heap available for use.

Attachments

    Outcomes