Support Article

Http 404 and 500 errors in Tomcat server

SA-36372

Summary



User is constantly getting HTTP 404 and 500 error codes on Tomcat Server logs, particularly during the execution of pyActivity=pyDeleteDocumentPg.


Error Messages



10.212.xxx 172.22.101.yy apollo.prod.alere.com [21/Mar/2017:22:56:05 -0400] GET /prweb/PRWebLDAP1/a9E6wnkc8Fwq7wDpVvVUKAmu1aEUvwdQ*/!TABTHREAD0?pyActivity=pyDeleteDocumentPg&pzFromFrame=&pzPrimaryPageName=TabGapHistory&pzHarnessID=HID2086FF3E434C49DA339E230DF5A911D6&pyPagesToRemove=D_UITemplateMeta HTTP/1.1 500 2416 Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0; KTXN) like Gecko http://apollo.prod.alere.com/prweb/PRWebLDAP1/a9E6wnkc8Fwq7wDpVvVUKAmu1aEUvwdQ*/!STANDARD?pzPostData=-942998663 4 http-bio-8001-exec-1738 H58F7C92CA4BE51F0C507F809E9F5321D 2D5AD14B6D84F0FEF11593F729BF800A IAC-NonGateway=%20e3be66af3fe5e35b241a1396f9dc0c6c; JSESSIONID=2D5AD14B6D84F0FEF11593F729BF800A; Pega-RULES=H58F7C92CA4BE51F0C507F809E9F5321D

host = ttapppegacc01 linux_server
source = /opt/apache-tomcat/7.0.64-1/logs/localhost_access_log.2017-03-21.log
sourcetype = apollo:prod:tomcat_access


Steps to Reproduce



Not Available

Root Cause



An issue in the custom application code or rules.

Custom activity is calling for logging off and it is not enabling the parentWindow.logout to true in
pzpega_ui_doc_lifecycle.js, which will call the pyDeleteDocumentPg activity and causes the issue.



Resolution



Perform the following local-change:

Designing the custom log out activity in a way that it will call the custom code and the Out-of-the-box (OOTB) logoff activity in custom java script file which will resolve the issue.

Published April 12, 2017 - Updated May 3, 2017

Have a question? Get answers now.

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