Cisco Process Orchestrator: Increase Java Heap Size

Available Languages

Download Options

  • PDF     (5.9 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (72.3 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (65.7 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:June 12, 2017
Document ID:113007

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes how to increase the Java heap size in the Cisco Process Orchestrator (CPO) server configuration file.

    Prerequisites

    Requirements

    There are no specific requirements for this document.

    Components Used

    The information in this document is based on CPO 3.0 or later

    The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

    Problem

    The user might find the need to increase their Java heap size if they see connectivity issues in any Java-related applications, general failures in those applications, or have system crashes due to Java components.

    Solution

    The Java heap size needs to be increased in the CPO server configuration file.

    Complete these steps:

    1. Go to the CPO install directory (for example, C:\Program Files\Cisco\Process Orchestrator).

    2. Stop the CPO Service.

    3. Edit the Tidal.Automation.Server.Exe.Config file.

    4. Locate the <Tidal.Scheduler.Common.Properties.Settings> tag.

    5. Locate the <setting name="AdapterHostJMVOptions" serializeAs="String"> tag. If it does not exist, create it and close the tag with a </setting> tag.

    6. Inside the AdapterHost tag, change the value to <value>-Xms16m -Xmx512m</value>.

      Note: You might have to make the second value -Xmx1024m if you have a larger system and need a larger heap.

    7. The total entry in the logs should appear as:

      <setting name="AdapterHostJVMOptions" serializeAs="String"> <value>-Xms16m 
    -Xmx512m</value> </setting>

    8. Save the Config file.

    9. Restart the CPO Service.

    TAC Authored

    Contributed by Cisco Engineers

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products