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

Problems with one node : Not processing requests

SA-3449
SUMMARY

A developer working in a three PRPC node environment observes that after installing a series of software fixes, and then backing out those software fixes, two PRPC nodes restart without trouble.  However, the third PRPC node restarts, but will not permit users to login.

ERROR MESSAGES

No error messages are provided on screen.  There are errors in the Pega Logfile, but none that are directly attributable to the login problem.  Users attempting to login will enter login credentials at the login screen, but then after pressing SUBMIT, the system appears to hang - users are unable to login.

STEPS TO REPRODUCE

Shutdown and restart the PRPC node, and then attempt to login.  Users are unable to login to the node at this point.

ROOT CAUSE

Root cause was attributed to the backout of previously installed PRPC software fixes: after backing out the fixes and then restarting the PRPC nodes, two nodes worked fine, but the third did not.

RESOLUTION

This issue is resolved through the following local change:

- Shutdown all PRPC nodes
- Purge the PegaRULES Database Cache tables
- Purge all nodes' Explicit Temp Directory
- Restart/Test All Nodes
Suggest Edit

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