This message was deleted.

You need to set in in

gradle.properties

file like this

org.gradle.jvmargs=-Xmx4g -Xms4g -XX:MaxMetaspaceSize=2048m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

Please do not split topics across several threads. This makes following the conversation in the threads view very hard as the context of the other messages is missing. If you have additional information either edit the original message or post to its thread. Regarding the problem,

JAVA_OPTS

sets the values for the ultra-thin CLI program.

org.gradle.jvmargs

sets the values for the Gradle daemon. Both do not help at all when you get OOM during test execution as this happens in a separate test worker process. Configure the

maxMemory

property (or how it is called) on the respective

Test

task instead.

Yeap, just found that I miss this part 🙂

Thanks Vampire. Increased memory heap size to 4GB but still the same issue

I thought that you didn't want to set a max space size for meta as there's also the max/min free space ratio that can cause OOM errrors as well. Max defaults to 70 and min defaults to 30. If you set a max that causes either of these ratios to get misaligned, you can also cause an OOO error as well.

sounds like it could be a memory leak, maybe there should be some clean up logic which would deallocate some items, or multiple spring contexts being created for the integration test? im not sure i would immediately look to something on the gradle layer for this issue

Thanks David & Daniel.. This issue is only with Windows Machine and Mac users are able to run this tests successfully

Maybe use the Gradle profiler to get some insights?