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

Costly DB Operation resulting Application performance



All MQ Listeners were using stateless unauthenticated service request in PRPC v5.4.

Following an upgrade from PRPC v5.4 to v6.1, the MQ listener configurations were changed to be authenticated services. 

Further to this MQ listener configuration change, a high MQ transaction load may cause sporadic performance issues.

This is due to the operator authentication process now invoked by the MQ configuration during each invocation, resulting in concurrent DB update operations which cause contention.

Error Messages

The MQ listener requestors may exhibit time-out exceptions,  a DB monitoring tool may expose "Buffer Busy Wait" or "row lock waits" on associated tables.

Steps to Reproduce

Sporadic in nature, requires high volume of MQ Listener transaction processing to exhibit DB buffer wait/row lock wait on pr_operator table. 

In this scenario, each request processed by the MQ listener results in an update to the pr_operator table to authenticate the operator nominated in the MQ listener rule form. This can result in DB row lock issues when there are large volumes of concurrent requests.


A Local-Change can be applied to prevent the Operator ID for the Listener having to update the pr_operator table.
In order to prevent the update of the OperatorID during authentication the following steps should be employed:
1. add a property named "extAssignFlag" to the Data-Admin-Operator-ID class
2. create and run a onetime activity which sets the value of the "extAssignFlag" property to any value
This should prevent the system from updating the pr_operators table when PRPC authenticates said operator.


Published June 12, 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