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

Request redirects to a different apache when audit is opened



User requests are routed to a different apache when user is actively working in Pega application. Unexpected error observed in the application.

Error Messages

Not Applicable

Steps to Reproduce

There is no specific use case to reproduce the behavior.

Root Cause

A defect or configuration issue in the operating environment. From the fiddler trace output, JSessionID cookie is changing during an active user session. Expected behavior is that load balancer will route the request to same Pega server as long as user session is valid.


Implement the following change to the operating environment:

Have the load balancer admin make necessary changes to address the problem with the sticky session issue.

Published October 5, 2015 - 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