Question
Wells Fargo
IN
Last activity: 20 Jun 2016 9:42 EDT
New JSESSION ID for every server request of single user session
We have noticed that pega is generating new JSESSION ID for every single server request from a pega web browser of a single user session. Also, we noticed that Pega-RULES session ID is remaining constant throughout the user session.
Is this an expected behavior(JSESSION ID getting changed for every server request)? If so, what is the rational behind having the JSESSION ID changed and Pega-RULES session id remaining constant?
Also, we have option to configure the JSESSION ID in the app server settings while we don't have any setting related to Pega-RULES session id. How is pega-Rules session ID managed?
Pegasystems Inc.
US
Pega requires sticky session in your load balancer/web server configuration. Once you do that, the JSessionID should be the same from the same user session. Refer to this link: https://pdn.pega.com/load-balancing-multi-node-cluster
JP Morgan Chase
IN
Does this mean, if I don't set this configuration, the JSESSIONID changes continuously even though the Pega-RULES session ID remains constant. What is the reason behind this architecture?
AA
GB
Sandeep,
Did you get anywhere with this problem? Is this working fine for you now?
Would like to know if there is a resolution. We are into similar problems with session ID.