Question
Issue with Gatling Scripts
We are trying to perform load testing of an application using Gatling tool. We have noticed that when executing a recorded scenario via Gatling, Pega is losing transaction boundaries. We see the following message in logs after the first commit in performed through the script:
2018-06-18 04:26:41,871 [http-nio-8070-exec-6] [TABTHREAD1] [ ] [ NMQ:01.01.01] ( mgmt.base.ThreadUITransaction) ERROR nmq.tal.xx.com|xx.xx.xx.xx CSPlanner2 - ERROR: posted transaction id 'be5828c5bea8678175038c305b1149ce' for frame 'pyWorkPage' DOES NOT match record 'cd264acbd3cb53b561ed5d2864a26feb'
The above problem occurs ONLY while executing scripts through Gatling. The same scenario when run manually works fine.
Hello TuhinG79, it looks like that you run the recorded simulation, and encounters a mismatching request. The best thing to do is capture the first GET response and grep the SessionID (e.g.
.get("/prweb/mFW9vHBT7hxOijRsFawQ3gjY0WwvMBOc*/!STANDARD")
)
insert the grepped sessionID (as a val between {}) in your copy of the recorded simulation and put it in your ChainBuilder. A simple example for login into Pega is like this:
Hope this is getting you there.
Grtz. Erik van der Made
Test Consultant
Valori Chapter Pega