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.
Steps to Reproduce
There is no specific use case to reproduce the behavior.
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.
0% found this useful