i used both gatling 2.2 and tried 2.2.1 also, whenever i get status code 500 error or 4xx error, the test execution gets completed, but not the Gatling execution, it keeps running in a loop every 5 secs and generating huge amount of simulation.log.
everytime i had to kill the job and manually generate the gatling report. its frustrating, never had this issue before in previous versions.
Example, when i get this type of error,
14:21:12.151 [WARN ] i.g.h.a.ResponseProcessor - Request 'VlidatesdfsfsPayment' failed: status.find.is(200), but actually found 401
======>> LATENCY: 2058 miliseconds
[Fatal Error] :1:1: Content is not allowed in prolog.
14:21:12.167 [ERROR] i.g.c.a.b.SessionHookBuilder$$anon$1 - 'hook-6' crashed on session Session(EISLoadScenario,3,Map(mUsdfsdfserID -> 23423423423, sdfsdfsdmID -> 234234234234, gatling.http.cache.dns -> io.gatling.http.resolver.ShuffleJdkNameResolver@4d5a74f1, sdfdsPayload -> {