This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

You can tune the Java Virtual Machine (JVM) settings to make a production system more efficient. 

You can configure the JVM parameters in the <ESB_HOME>/bin/wso2server.bat file (on Windows) or the <ESB_HOME>/bin/wso2server.sh file (on Linux/Solaris). Following are the most important JVM parameters you need to configure:

  • Maximum Heap Memory Allocation (Xmx) - This parameter sets the maximum heap memory allocated for the JVM. Increasing the memory allocation increases the memory available for the ESB, which results in increasing the maximum TPS and reducing the latency. We recommend al least 2 GB of heap memory allocation for instances.
    For example, If you want to set 2 GB as the maximum heap memory size, you need to configure the parameter as follows:

    -Xms2048m -Xmx2048m -XX:MaxPermSize=1024m

    Here, 
    Xmx is the maximum memory allocation pool for a JVM.
    Xms is the initial memory allocation pool.
    XX:MaxPermSize is the permanent space where the classes, methods, internalized strings, and similar objects used by the VM are stored and never deallocated.

    When using JDK 1.8.*, you do not need to specify MaxPermSize since it has been removed with this version of Java.

  • Entity Expansion - If one or more worker nodes in a clustered deployment require access to the management console, you need to increase the entity expansion limit. The default entity expansion limit is 64000.
    If you want to set expansion limit is 100000, you need to configure the parameter as follows:

    -DentityExpansionLimit=100000

 

  • No labels