TuhinG79 Member since 2018 2 posts
Deere & Company
Posted: 2 years ago
Last activity: 2 years 3 months ago

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|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.

Low-Code App Development Testing Applications
Moderation Team has archived post
Share this page LinkedIn