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 behavior incorrect



User traces a data page loaded with a complex activity involving a lot of loops on a voluminous data structure. User traces Run on a data page which uses a Connector simulation to load itself. The user also traces a test activity that is created to invoke the same connector. The connector is in the simulation mode. No issues occur in both the cases. However, the below stack trace displays in the logs on tracing the data page:

937 [default task-6] [TABTHREAD8][ ][Client:](erated.pega_uiengine_pzcontrol)ERROR sld03503.n18.| ZEX9650 - pg empty after  
937 [default task-6] [TABTHREAD8][ ][Client:](erated.pega_uiengine_pzcontrol)ERROR sld03503.n18.| ZEX9650 - pg empty after  
958 [default task-6] [TABTHREAD8][ ][Client:](erated.pega_uiengine_pzcontrol)ERROR sld03503.n18.| ZEX9650 - pg empty after  
958 [default task-6] [TABTHREAD8][ ][Client:](erated.pega_uiengine_pzcontrol)ERROR sld03503.n18.| ZEX9650 - pg empty after  
301 [default task-80] [STANDARD][ ][Client:](tion.pxLogErrorMessage.Default)INFO|ZEX9650 - DTReq.LogMessage: <?xml version="1.0"encoding="UTF-8"?> <!--Sample XML file generated by XMLSpy v2010 rel.3(x64)<rgcu:RGCU xsi:schemaLocation=EMET_001>CF00</rgcu:EMET_001> <rgcu:FLUX><rgcu:FLUX_002>L01V01</rgcu:FLUX_002> </rgcu:FLUX><rgcu:MESS xsi:type="rgcu:DGENERAL"><rgcu:MESS_001>05</rgcu:MESS_001> <rgcu:MESS_002>20</rgcu:MESS_002><rgcu:ASSU </rgcu:ASSU_001> <rgcu:ASSU_002>a</rgcu:ASSU_002><rgcu:ASSU_003>RCARRAVA</rgcu:ASSU_003><rgcu:ASSU_004>RCARRAVA</rgcu:ASSU_004> <rgcu:ASSU_005>Georges</rgcu:ASSU_005> <rgcu:ASSU_006>01</rgcu:ASSU_006><rgcu:ASSU_007>20011970</rgcu:ASSU_007> <rgcu:ASSU_008>Tours</rgcu:ASSU_008> <rgcu:ASSU_009>37</rgcu:ASSU_009> <rgcu:ASSU_010>FR</rgcu:ASSU_010> <rgcu:G008> <rgcu:G008_005></rgcu:G008_005> <rgcu:G008_007>04</rgcu:G008_007><rgcu:G008_011>07</rgcu:G008_011> </rgcu:G008></rgcu:ASSU> </rgcu:MESS </rgcu:EMET> <rgcu:TOTA> <rgcu:TOTA_001>0.0</rgcu:TOTA_001> <rgcu:TOTA_002>0.0</rgcu:TOTA_002> </rgcu:TOTA> </rgcu:RGCU> 

The Tracer causes death freeze of the session. The browser must be closed to be able to start a session and the previous session must be closed using the Admin portal. The data pages are traced incorrectly on Pega 8.1.1. However, they are traced correctly on Pega 7.4. This affects the activities. The activities are traced correctly on Pega 7.4 and traced incorrectly on Pega 8.1.1.

Nothing is traced while tracing a data page. Sometimes the technical activities related to running the data page are traced in the Tracer. However, the activity that is invoked to load the data page is not traced. However, nothing displays in the logs.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a data page
  2. Click Actions
  3. Click Trace

Root Cause

A defect or configuration issue in the operating environment. An issue with jboss. TimeoutException occurs in the Fiddler Trace.  


Perform the following local-change:
  1. Remove the Distributable tag from the prconfig.xml file
  2. Restart the server


Published December 2, 2021

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