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

404 error in the UAT env

SA-3472

Summary


accessing UAT PRPC application throws 404 error. SSO login URL did not work while the PRServlet url worked.

Error Messages


404 error on the screen. 

Steps to Reproduce


- access the UAT url;
- issue is sporadic.

Root Cause


From the error message '404' error message request was not reaching pega - no pega cookie in the response header of this error in fiddler trace. the proxy log shows http request to one of the weblogic nodes returned 404. further checking proxy log shows, all the requests to that node returned 404. Directly accessing that problematic WebLogic node also threw same 404 error, while direct access to other weblogic node is working fine. checked the web.xml of the both the nodes and found differences in web.xml. recently there was a hfix installation was deployed in these nodes. 

Resolution


correcting the servlet mapping in web.xml for the problematic node resolved the problem.

Published January 31, 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?

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