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

500 Server Errors : pyDeleteDocumentPg called after logoff

SA-9625

Summary



Server error 500 occurs in two GUI based applications. An increased number of 500 errors are observed in the server logs.

Error Messages



10.188.100.157 - [24/Feb/2015:12:31:29 -0800] "GET /prweb/PRServlet/i_LC2_L_GFJsMaOa4QxWBOuRaEiBsrQP*/!Developer?pyActivity=pyDeleteDocumentPg&=%26&pzFromFrame=&pzPrimaryPageName=RH_5&pyPagesToRemove= HTTP/1.1" 500 2416

Steps to Reproduce



This issue does not occur in every instance and appears to be related to some clean up activities occurring at the end of a flow. The log entries indicate that the pyDeleteDocument activity is attempting to remove a few top level pages. These logs indicate that the activity is successfully processing/removing the pages as seen below:

1. One or more successful pages removed.

pyActivity=pyDeleteDocumentPg&=%26&pzFromFrame=&pzPrimaryPageName=RH_1&pyPagesToRemove= HTTP/1.1" 200 21

2. Then this log entry indicates that the activity Code-Security.Log runs.

10.188.100.157 - [24/Feb/2015:12:31:29 -0800] "GET /prweb/PRServlet/i_LC2_L_GFJsMaOa4QxWBOuRaEiBsrQP*/!Developer?pyActivity=Code-Security.LogOff&pzAuth=guest HTTP/1.1" 303 0

3. When the system then tries to continue deleting pages 500 error occurs.

10.188.100.157 - [24/Feb/2015:12:31:29 -0800] "GET /prweb/PRServlet/i_LC2_L_GFJsMaOa4QxWBOuRaEiBsrQP*/!Developer?pyActivity=pyDeleteDocumentPg&=%26&pzFromFrame=&pzPrimaryPageName=RH_5&pyPagesToRemove= HTTP/1.1" 500 2416


Root Cause



The AJAX call to the pyDeleteDocumentPg activity is part of the window onBeforeUnload event if the window is a harness. This is done in the pzpega_ui_doc_lifecycle.js harnessOnBeforeUnload function. 

This should not be called if the user has triggered a logoff. 


Resolution



This issue is resolved by HFix-21685 for Pega 7.1.5 and is further resolved in Pega 7.1.7.

The call to pyDeleteDocumentPg is not called if logoff has been triggered. 
Suggest Edit

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