Error In version 2.0.0-SNAPSHOT - when deleting cookies

Hi,
I have logout step in my scenarios.
I have recently changed version of gatling to the newest one:2.0.0-SNAPSHOT (because it solves some bugs that annoyed me).

Now I have another issue :). New version isn’t handling my logout step very well.
Here is stack-trace:
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.263 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.264 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
17:56:20.264 [ERROR] i.g.h.a.AsyncHandlerActor - AsyncHandlerActor crashed on unknown message None, dropping
[ERROR] [04/28/2014 17:56:20.262] [GatlingSystem-akka.actor.default-dispatcher-19] [akka://GatlingSystem/user/$c] String index out of range: 0
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(String.java:658)
at io.gatling.http.cookie.CookieJar$.cookiePath(CookieJar.scala:61)
at io.gatling.http.cookie.CookieJar$$anonfun$1.apply(CookieJar.scala:107)
at io.gatling.http.cookie.CookieJar$$anonfun$1.apply(CookieJar.scala:103)
at scala.collection.LinearSeqOptimized$class.foldLeft(LinearSeqOptimized.scala:111)
at scala.collection.immutable.List.foldLeft(List.scala:84)
at io.gatling.http.cookie.CookieJar.add(CookieJar.scala:102)
at io.gatling.http.cookie.CookieJar.add(CookieJar.scala:97)
at io.gatling.http.cookie.CookieHandling$.storeCookies(CookieHandling.scala:47)
at io.gatling.http.ahc.AsyncHandlerActor$$anonfun$2.apply(AsyncHandlerActor.scala:271)
at io.gatling.http.ahc.AsyncHandlerActor$$anonfun$2.apply(AsyncHandlerActor.scala:271)
at io.gatling.http.ahc.AsyncHandlerActor.redirect$1(AsyncHandlerActor.scala:222)
at io.gatling.http.ahc.AsyncHandlerActor.io$gatling$http$ahc$AsyncHandlerActor$$processResponse(AsyncHandlerActor.scala:274)
at io.gatling.http.ahc.AsyncHandlerActor$$anonfun$receive$1.applyOrElse(AsyncHandlerActor.scala:90)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:498)
at akka.actor.ActorCell.invoke(ActorCell.scala:456)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:237)
at akka.dispatch.Mailbox.run(Mailbox.scala:219)
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:385)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

Here is what my logout step does:
Set-CookieJSESSIONID=""; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=""
so basically - it deletes cookies - an it looks like gatling still tries to do something with those deleted cookies (without checking if they still exist)
Can you help me in any way? can you fix the issue?

btw. nice tool - thanks for creating it!

I’m trying to reproduce.
Can you give us the associated line in the Gatling script ?

thanks for reporting.
Nicolas

Nevermind. Got it, pushing a patch.

https://github.com/excilys/gatling/commit/ca9f31a0817940c505ac63a809f3b540492e5b0d

In the next Travis build, the issue should be fixed.

cheers
Nicolas

Thanks for really quick reaction!

I have checked if it was fixed with latest snapshot and it is fixed - so THANK YOU, you can close this topic
btw. good job - bugfix released over night :slight_smile:

W dniu wtorek, 29 kwietnia 2014 11:04:42 UTC+2 użytkownik Mariusz Panek napisał:

Thanks for the feedback.