Changing the JVM Heap Size Used by Microservices Runtime
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 Microservices Runtime 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 parameters specified in the setenv.bat/sh file.
Parameter | Description |
JAVA_MIN_MEM | The minimum heap size. The default value is 256MB. |
JAVA_MAX_MEM | The maximum heap size. The default value is 1024MB. |
Your capacity planning and performance analysis should indicate whether you need to set higher maximum and minimum heap size values.
Note:
You can change the heap size for Microservices Runtime at start up by starting Microservices Runtime from the command line and supplying the JAVA_MAX_MEM and JAVA_MIN_MEM environment variables. Using the environment variables allows you to override the values set for Microservices Runtime in the Integration Server_directory /bin/setenv.bat|sh file without having to edit the file itself.
To change the heap size for
Microservices Runtime1. Navigate to Integration Server_directory /bin and use a text editor to open the setenv.bat/sh file.
2. Set the JAVA_MIN_MEM and JAVA_MAX_MEM parameters so that they specify the minimum and maximum heap size required by Microservices Runtime.
3. Save the file.
4. Restart Microservices Runtime.