2.0.0-RC5 removed ahc properties

Gatling (Open-Source)
1

Hi guys,

After upgrading to 2.0.0-RC5 today I noticed the following lines in the log when starting my test:

21:45:29.999 [WARN ] i.g.c.c.GatlingConfiguration$ - Beware, property gatling.http.ahc.allowPoolingConnection is still defined but it was removed
21:45:30.004 [WARN ] i.g.c.c.GatlingConfiguration$ - Beware, property gatling.http.ahc.allowSslConnectionPool is still defined but it was removed
21:45:30.004 [WARN ] i.g.c.c.GatlingConfiguration$ - Beware, property gatling.http.ahc.requestTimeoutInMs is still defined but it was removed

My gatling.conf has the following values set for these properties

allowPoolingConnection = false # allow pooling HTTP connections (keep-alive header automatically added)
allowSslConnectionPool = false # allow pooling HTTPS connections (keep-alive header automatically added)
requestTimeoutInMs = 30000 # timeout of the requests

In the run I saw requests timing out at 60000 ms, so it seems the values in gatling.conf are not used. Does RC5 come with an updated gatling.conf?

Cheers

Daniel

2

Those properties were renamed in RC3 or something.
Just check gatling-default.conf in gatling-core.jar.

I guess we should log in error and mention the replacement.
https://github.com/gatling/gatling/issues/2202

3

Hi Stephane,

Thanks for your reply, actually I already checked the gatling-defaults.conf, I just overlooked the (slight) differences ;-S Time to go to sleep ...

Cheers

Daniel

4

Well, you’re right, those should properly be documented.