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

Rolling restarts are not transparent to active user

SA-28850

Summary



After High Availability is configured, existing users logged in are not transparently passed to the active server during a rolling restart scenario.

System Management Application (SMA) shows that the quiesce processes completes successfully after a server is disabled via the load balancer, and no active requestors are shown on the server being brought down.

Users experience unending load screens when taking actions and receive the error "PegaRULES Request Status error Too many identical requests in quiesce mode." when user attempts to close an open work object.


Error Messages



Too many identical requests in quiesce mode. Please see your system administrator. Unauthenticated or not available No ID available Unknown.


Steps to Reproduce

  1. Configure shared storage and update passivation path in prconfig.xml file.
  2. Apply redundancy across the infrastructure.
  3. Configure Load Balancer with Cookie persistence and give cookie name as 'cookie'.
  4. Make changes in prconfig file.xml per High Aavailability guide.
  5. Log into one of the server in cluster as a user (Non Quiesce admin).
  6. Disable the corresponding server in load balancer.
  7. Begin Quiesce on the server.
  8. Try to open work objects through the portal.


Root Cause



The root cause of the issue is due to a configuration problem in user's operating environment.

The cookie name was configured incorrectly.

Also, there was a one to one mapping between the Webserver and Application server in the
environment used for testing high availability.

Resolution



The following options are recommended:
  1. Update the cookie name to JSESSIONID.
  2. In-order for the routing to work, at-least two nodes should be mapped to a webserver. One can have multiple web servers, but each one needs to have more than one node to be routed to (as defined in the plugin-cfg.xml).

Published October 18, 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