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

Server is not responding interminently



Load balancer software is configured on two nodes.
Errow is observed sporadically when server is accessed through load balancer URL.

PRPC renders properly upon browser refresh.

Error Messages

Status info

Message Connection failed. Try again
Operator ID Unauthenticated or not available
Requestor ID No ID available
Engine Version Unknown

Steps to Reproduce

Not Applicable.

Root Cause

Root cause of the issue is problem in PRPC code.While making the changes for HttpOnly, response.setHeader method is used to set the cookies(eg:Pega-RULES, Pega-Captcha and other cookies). This overrides the headers that are already set with the same name(SET-COOKIE).
JSESSIONID is set even before Pega-RULES cookie in the response headers.
As JSESSIONID cookie and Pega-RULES cookie both share the same headername(SET-COOKIE), the first one is getting overridden.


Apply HFix-20419.

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