Unable to run OTK upgrade 4.4 to 4.4.1 or 4.5. During the upgrade, the policy manager fails with the following error:
Build Info:
Layer7 API Gateway Policy Manager 10.1.00.11620 build 11620, built 20210706173756 by teamcity at ${env.COMPUTERNAME}
System Properties:
java.version: 11.0.11
java.specification.version: 11
os.name: Windows 10
os.arch: x86
Memory Usage:
444,027,544 bytes: the amount of free memory in the Java Virtual Machine.
826,507,264 bytes: the total amount of memory in the Java virtual machine.
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.l7tech.console.util.f.call(Unknown Source)
at com.l7tech.console.util.f.call(Unknown Source)
at com.l7tech.gui.util.as.construct(Unknown Source)
at com.l7tech.gui.util.au.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
We have modified the Xmx setting to more than 1024M, but since it seems to be a 32 bit application the max possible value was around 1600M.
Is there any solution to either run the manager with more memory or decrease the memory requirements for the OTK upgrade?
Release : 10.1 OTK 4.4
Component :
Client is running OTK with multiple instance so 2gb of heap space is to small.
A Timeout Runtime Exception can occur if you do not have enough RAM to perform the upgrade.
Minimum memory for OTK should be at least 4 GB.
If you have multiple instances of the OTK or other solution kits installed, we suggest a minimum of 8 GB for the Layer7 API Gateway RAM
The Heap space error on the policy manager is not the root cause, increasing it and assigning it a 64bit JRE did not resolve the problem.
Besides the heap space error on the policy manager there was also a heap space error on the gateway which could be found in the ssg log.
Increasing the gateway's heap space memory from 2gb to 8gb will resolve the error.