MID Server memory issues
Last updated
Last updated
It has been observed in appliances with many CIs that some import processes have a big input load. In the event that the logs report some ECC timeout issues and/or the error java.lang.outofmemoryerror java heap space, it is most likely due to the mid server requiring more memory than is currently allocated, thus causing the MID Server to crash.
To resolve this issue, it is advisable to increase the heap space allocation in the agent/conf/wrapper-override.conf file of the MID Server:
The value that must be set in the property wrapper.java.maxmemory depends on the Server capacity and the amount of data to be inserted. This property is commented by default; therefore, it is necessary to uncomment it first.