hello,
I am trying to upgrade Gatling from 2.0.2 to 2.1.7, and at the same time Scala 2.10.4 → 2.11.8.
It turns out I have a problem with the (legacy) SignatureCalculator in use and the encoding of the space
exec(http(“encoding.message.create”)
.post("/api/sync")
.formParam(“foo”, “a b”)
.signatureCalculator(new MessagingSignatureCalculator)
.check(status.is(201))
It fails with the following req/resp:
aah, ok. So this is present in the 1.9.x-versions of async-http-client? I see that Gatling 2.1.7 is using com.ning:async-http-client:jar:1.9.30
Not possible to upgrade to 2.0.4, I guess, so this seems to be a showstopper?
Why not modify your custom Signature calculator?
And why only upgrade to 2.1.7 while latest is 2.2.1?
yes, I need to have a look at the SignatureCalculator to be able to fix this, I guess.
Gatling 2.2.1 requires JDK8, right? We are currently on Java 7, so would be a too big upgrade.
Gatling 2.2.1 requires JDK8, right? We are currently on Java 7, so would
be a too big upgrade.
- JDK7 has reached public end of life in April 2015
- JDK8 was released in March 2014, latest release is 8u92, so it's been
through lots of patches and is very stable
- JVM upgrade is usually a no brainer with huge benefits (except if you
run on some commercial platform you pay support for)
- Gatling is a load test tool, not your app that has to run in your
production environment, so it's objectively no big deal if it runs on a
different JVM than your app
*Stéphane Landelle*
*GatlingCorp CEO*
slandelle@gatling.io