Simulation finished, but actor doesn't terminated

[Gregory Melekh]

Hello Gatling Experts.

I encountered with following issue.

my Simulation finishing to run.

Gatling log prints "Simulation finished".

and then 

[INFO] [03/04/2015 11:45:53.507] [GatlingSystem-akka.actor.default-dispatcher-5] [akka://GatlingSystem/user/ConsoleDataWriter] Message [io.gatling.core.result.writer.Display$] from Actor[akka://GatlingSystem/user/ConsoleDataWriter#1731424849] to Actor[akka://GatlingSystem/user/ConsoleDataWriter#1731424849] was not delivered. [1] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.

report doesn't generated ,and process permanently stuck .

the flow is as following:

val sannity = group("sanity of all common action - 1 user"){

    //  exec(UserActions.getSignUpToken).pause(1 seconds)

     // .exec(UserActions.toChangeCookie).pause(1 seconds)

    //  .exec(UserActions.firstloginToPortal).pause(1 seconds)

      exec(UserActions.getLoginToken)

      .exec(UserActions.logintoportal).pause(1 seconds)

      .exec(UserActions.clickOnProjects).pause(1 seconds)

      .exec(UserActions.createProject).pause(1 seconds)

      .exec(UserActions.importProject).pause(1 seconds)

      .pause(30 seconds) // editing

      .exec(UserActions.lookAtSamples).pause(1 seconds)

      .exec(UserActions.clickOnExplore).pause(1 seconds)

      .exec(UserActions.lookAtSamples)

      .exec(UserActions.editFlow).pause(1 seconds)// editting

      .exec(session => {

          session

          .set("isOK", "None")

          .set("flowStartTime", System.currentTimeMillis())

          .apply(session)

            })

        .exec(UserActions.deploy).pause(50 seconds).exec(connectingModeGroup)

         .exec(session => {

          session

          .set("flowEndTime", (System.currentTimeMillis() - session("flowStartTime").as[Long]) /1000)

          .apply(session)

            })

        .exec(session =>{

          println("Deploy time of user "+session("username").as[String]+" = "+session("flowEndTime").as[String] + " seconds .")

          session

          })

        .exec(UserActions.endPoint).pause(1 seconds) 

        .exec(UserActions.deployInConnectedMode).pause(1 seconds) 

        // .repeat(4) { exec(UserActions.stopEnvironment).pause(30 seconds).exec(UserActions.startEnvironment) }

        .exec(UserActions.showSpaces).pause(1 seconds) 

        .exec(UserActions.clickOnAdvanced).pause(1 seconds) 

        .exec(UserActions.getProjectId)

        .exec(UserActions.getPrivateToken)

        .exec(UserActions.getAllExistingEndPoints)

         .exec(session =>{

           println("""session("endPoints").as[String] =    """+session("endPoints").as[String])

               new EndPointsHandler(session("endPoints").as[String],"HELLO MY CI","Load")         // here is scala code that creates additional simulation

          session

          }) 

        .exec(UserActions.logout)

        .exec(UserActions.verifyLogout)

      

  }

why this happened.

Any Ideas.

Thanks for advance. 

[Gregory Melekh]

This issue raised while using Gatling 2.1.4  

(Same behavior using bundle and maven-plugin.)

Bundle 2.0.3 works fine.

The report generates and message doesn't raised.

[Stéphane LANDELLE]

Would need a reproducer.

Cheers,

Stéphane Landelle

Lead developer

slan...@gatling.io

--
You received this message because you are subscribed to the Google Groups "Gatling User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gregory Melekh]

Hi Stéphane.

It was a configuration issue.

It Works.

Thanks.

[Stéphane LANDELLE]

Glad to hear :)

Stéphane Landelle

Lead developer

slan...@gatling.io