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

Contention for checking access rules for tracer events

SA-34713

Summary



Contention on Tracer internals: A check for sending Tracer events when a user is denied access to a role via Rule-Access-* rules. This is showing up in YourKit as blocking interactive HTTP users ~30-40% of the time.

Error Messages



Not Applicable


Steps to Reproduce



No specific steps, during performance profiling user observed that there is some contention when they check for tracer to log trace events for access denials


Root Cause



There is unnecessary contention in the environment for a check related to logging trace events for access denied requests.

Resolution



Apply HFix-32859
Description of Changes:
A prconfig switch to disable these tracer checks, since we know that tracer is not used in census
Additional Installation Instructions:
the prconfig to enable is:tracer/Enable Access Denied Events.The default is true. It should be made false to enable this optimization.

Suggest Edit

Published March 10, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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