Hi
Thanks for helping out here unfortunately it still have the problem. I looked at the processes when my gatling test runs, I saw two java processes, the 1st one is started by me and the 2nd one I believed is started by gatling.
In the 2nd java process, there is a -Xmx1G config, I am suspecting this is the culprit that caused my OutOfDirectMemory error, how do I change this process setting? It is invoked by gatling i think
process 1:
root 1442480 1442437 0 01:08 pts/0 00:00:11 /bin/java -Xmx4096M -classpath /opt/maven/boot/plexus-classworlds-2.6.0.jar -Dclassworlds.conf=/opt/maven/bin/m2.conf -Dmaven.home=/opt/maven -Dlibrary.jansi.path=/opt/maven/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/var/lib/jenkins/workspace/QA_Performance_Test org.codehaus.plexus.classworlds.launcher.Launcher gatling:test -Dgatling.simulationClass=ClientWorkflowSimulation
process 2:
root 1442572 1442480 16 01:08 pts/0 00:05:20 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.302.b08-0.el8_4.x86_64/jre/bin/java -server -Xmx1G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:+HeapDumpOnOutOfMemoryError -XX:MaxInlineLevel=20 -XX:MaxTrivialSize=12 -XX:-UseBiasedLocking -Djdk.net.URLClassPath.disableClassPathURLCheck=true -Dgatling.simulationClass=ClientWorkflowSimulation -Dlibrary.jansi.path=/opt/maven/lib/jansi-native -jar /tmp/gatlingbooter7006757122097394169.jar io.gatling.app.Gatling /tmp/gatling-maven-plugin-1976583146813467598.args