Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Transaction ID mismatch during case processing

SA-12452

Summary



When working with two separate windows in CPM, a command fails occasionally.  Error message are observed in the PegaRULES log file.

Error Messages



2015-03-10 16:18:44,484 [fault (self-tuning)'] [ STANDARD] [ xxx] (ntext.base.ThreadUITransaction) .... ERROR: posted transaction id 'fc2b2195344ca3576b551d23350e6671' for frame 'ActionFrame' DOES NOT match record '27a80cc47ddd1ce421b51b6239917c5f'

Steps to Reproduce



Launch another window and work interchangeably from one window and then the other. The error is intermittent.

Root Cause



In the PRPC 5.4 release, the use of multiple threads to allow simultaneous processing of different work objects in different database transactions was still in early development. One of the big weaknesses in this early architecture was the fact that the current transaction ID was kept on the single pxRequestor clipboard page. Although each thread would have its own transaction ID, it was the responsibility of the current active thread to place its transaction ID into the one pxRequestor page and keep it maintained.

This design proved fairly fragile.  Occasionally, the transaction ID from one thread was not removed from the pxRequestor page, and when the next thread (the other window) became active. The PRPC Engine still believed that the active transaction ID was the one from the previous thread, with the resulting error.

There was a complete redesign which eliminated the use of the (one) pxRequestor page to track the transaction ID, and instead had each pxThread page (there is one for each thread) maintain its own transaction ID.  This design proved much more robust, and is the one still in use in the current Pega 7 series.


Resolution



The changes in support of the new design are considerable and cannot be inserted as a hotfix.  Either upgrade to a new release (Pega 7), or stop the user behavior which causes the error.

Published July 29, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us