Question

9
Replies
7055
Views
Rob Jago (Rob_Jago)
Rulesware
Senior Consultant
Rulesware
CA
Rob_Jago Member since 2015 41 posts
Rulesware
Posted: January 13, 2017
Last activity: February 6, 2017
Posted: 13 Jan 2017 9:21 EST
Last activity: 6 Feb 2017 0:45 EST
Closed
Solved

posted transaction ID for frame DOES NOT match record

Hello,

using Pega 7.1.8.

While investigating slow request/response times in the Pega application. I saw the following error messages in the log files:

posted transaction id 'xxxxxx' for frame 'pyWorkPage' DOES NOT match record 'yyyyyyy'.

The values for 'xxxxxx' and 'yyyyyyy' are different on each log entry and are not linked between the lines...
I found this on the PDN but speaks of Pega 6.2 and the appropriate hotfix. (because I am using 7.1.8, I didn't think it was an issue)

https://pdn.pega.com/support-articles/error-posted-transaction-id-frame-does-not-match-record

Is this related / linked with the performance slowness (a symptom, cause or side-effect)?

performance slowness is best described as (click button and wait 3 - 5 seconds before a new subcase is created and new assignment shown)

***Updated by moderator: Lochan to add SR details***

System Administration Support Case Created
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.