Changing the JVM Heap Size Used by Integration Server
The JVM heap or on-heap size indicates how much memory is allotted for server processes. At some point, you might need to increase the minimum and maximum heap size to ensure that the JVM that Integration Server uses does not run out of memory. You will want to consider the heap size when you configure your server to publish and subscribe to documents and when you configure an on-heap cache.
The heap size is controlled by the following Java properties specified in the custom_wrapper.conf file.
Property | Description |
wrapper.java.initmemory | The minimum heap size. The default value is 256 MB. |
wrapper.java.maxmemory | The maximum heap size. The default value is 1024 MB. |
Your capacity planning and performance analysis should indicate whether you need to set higher maximum and minimum heap size values.
Note: Microservices Runtime does not use the Java Service Wrapper and the custom_wrapper.conf file. To change the memory settings for Microservices Runtime, use a text editor to set the JAVA_MIN_MEM and JAVA_MAX_MEM properties in: Integration Server_directory /bin/setenv.bat(sh).
To change the heap size
1. Open the custom_wrapper.conf file in a text editor. You can find the custom_wrapper.conf file in the following location:
Software AG_directory \profiles\IS_instance_name\configuration
2. Set the wrapper.java.initmemory and wrapper.java.maxmemory parameters so that they specify the minimum and maximum heap size required by Integration Server. For example:
wrapper.java.initmemory=256
wrapper.java.maxmemory=512
3. Save and close the file.
4. Restart Integration Server.