2.0.0-M4?

Hi Stephane,

I am sorry but I do not see the jars of 2.0.0-M4 inside http://repository.excilys.com/content/repositories/releases/io/gatling/, the last update being done in July?

Thanks,
Divya

We haven’t released M4 yet. See progress here: https://github.com/excilys/gatling/issues?milestone=44&page=1&state=open

Also note that it will be deployed on maven central and not hosted on Excilys’ repo.

could you just give a snapshot version with the feature of two http requests running parallely? the feature which was available in 1.5.2 but was removed in the latest version? This is my humble request as I was eagerly waiting for this feature to be released along with 2.0.0-M4 so that I can proceed with my requirement? Kindly consider.

https://github.com/excilys/gatling/wiki/Continuous-Integration

Thanks a lot, its working.

Cool.

Note that it still lack the recorder counterpart of this feature: https://github.com/excilys/gatling/issues/1569

Hi Stephane,

I am facing an issue with the latest jars. I have a scenario where ‘Set-Cookie: JSESSIONID=98C138CAEF9A8FF75D09195726E39F6E;’ from the previous response headers will be passed on to subsequent requests automatically so that each request can be tracked to a sessionid. This used to work in 2.0.0-M3a. But in the latest one, its not working. The request is received on the server without sessionid. I verified the two requests for 2.0.0-M3a and latest. Below are the differences. Could you help?

2.0.-M3a:

Session:

Session(CometAdapter,0,Map(accountName → 011, accountPwd → t00, tn → 18567806771, gatling.http.cookies → CookieStore=Map(//11.22.33.44 → List(Cookie: domain=11.22.33.44, name=JSESSIONID, value=0F460BF181F2FCD1CC57B0C6CB7560F6, path=/CometAdapter/, maxAge=-1, secure=false)), logintoken → PHNhbW),1387562077343,35,List(),List(OK),List(),List())

Latest jar:

Session:

Session(CometAdapter,4685099582728390556-0,Map(accountName → 011, accountPwd → t00, tn → 18567806771, gatling.http.cookies → CookieJar(Map(11.22.33.44 → List(Cookie: domain=11.22.33.44, name=JSESSIONID, value=DD48651AE18507CCE734ECC585BA069F, path=/CometAdapter/, maxAge=-1, secure=false))), logintoken → PHNhbW),1387561796904,1,List(),List(KO),List(),List())

Could you share an example of a Set-Cookie response header, and expected request with Cookie header (from firebug or Google Chrome dev tools), please?

Stephane, I have the info from Jmeter. Please see the details.

The response header from first request is below:
Response headers:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=98C138CAEF9A8FF75D09195726E39F6E;

and request header for subsequent requests should be like this:

Cookie Data:
JSESSIONID=98C138CAEF9A8FF75D09195726E39F6E

Request Headers:
Connection: keep-alive
Content-Length: 46
Content-Type: text/plain;

So the original Set-Cookie header doesn’t contain any path nor domain, and the 2nd request is on the domain as the 1st one, right?

sorry it does contain path:

Response headers:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=98C138CAEF9A8FF75D09195726E39F6E; Path=/CometAdapter/; HttpOnly
Transfer-Encoding: chunked

OK, and is the 2nd request is on the same path or a child one?

on the same path, this is basically a servlet - a post request sends back a sessionid, subsequent get, put or delete uses the sessionid from post for tracking the user.

Hi STephane,

Is it an issue in my code or error in latest jar?

That was indeed a bug: https://github.com/excilys/gatling/issues/1570

Fixed, thanks for reporting.
You will find an updated snapshot on Sonatype in ~30min.

Cheers,

Stéphane

+1 on a M4 release. The M3 release still depends on an old Akka version, that conflicts with our 2.2.3 version.

We’re almost there: https://github.com/excilys/gatling/issues?milestone=44&state=open
You can use snapshots until then (a matter of weeks I guess)