Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Gatling hangs at compile time on oracle jdk/jre > 8u151

See original GitHub issue

I’m not sure if this issue should be submited here or rather to gatling-maven-plugin project, I will however give it a try.

We’ve recently realised our gatling tests started hanging infinitely from time to time, during the compilation phase. This happened after upgrading java from 8u151 to 8u152 and further.

I have an example project that should reproduce the bug. This is a maven project with simple simulation (BasicSimulation from here https://gatling.io/docs/2.3/quickstart/). It also uses maven-gatling-plugin. I run gatling simulation by executing mvn clean test. The process is then repeated multiple times.

To simulate multiple java environments, I assume you have docker installed on your host. Here’s how to reproduce the issue:

Clone the following repo https://github.com/slnowak/gatling-bug.git
Checkout java8-u151 branch.
Build docker image: docker build -t gatling:java8-u151 .
Start the container docker run gatling:java8-u151 . This will run mvn clean test 10 times within a container with installed oracle jre 8u151. After that, docker container exits with 0, which means the entire load testing process is done.
Checkout java8-u162 branch.
Build docker image: docker build -t gatling:java8-u162 .
Start the container docker run gatling:java8-u162 . This will run mvn clean test 10 times within a container with installed oracle jre 8u162. This time however, the process will hang at some point with 23:29:33.033 [main][WARN ][ZincCompiler.scala:142] i.g.c.ZincCompiler$ - Pruning sources from previous analysis, due to incompatible CompileSetup.
The process could be nondeterministic - I just had to run docker run gatling:java8-u162 twice to reproduce the issue, so please repeat if necessary