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

Tracer getting disabled after tracer file size reaching 1024 MB

SA-27204

Summary



User is getting a high priority issue in production and remote tracing of procom agent is required to analyze the issue. Tracer is generating a file in temp directory, as soon as this file is reaching 1024 MB, tracer is getting disabled and not tracing any further.
In user environment, Maximum number of events is set to 0 and 500000000000, but same behavior persists.
Selecting only required rulesets, events would not help in this case.


 

Error Messages



Not Applicable


Steps to Reproduce



Do a remote tracing of procom agent, and make sure this tracing generate a file of size greater than 1024 MB, tracer gets disabled


Root Cause



By default, file attachments are restricted to 1 gigabyte in size. You can set a larger or smaller limit with the prconfig.xml file setting.

Resolution



This issue is resolved through the following local-change:

Place the below code in the prconfig.xml:

<env name="Initialization/MaximumFileUploadSizeMB" value="nn" /> 

​where nn is the size in megabytes. You need to restart the server.

 

Published September 3, 2016 - 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?

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