Question

1
Replies
90
Views
Sai_INCESSANT Member since 2014 14 posts
Incessant Technologies Pvt Ltd
Posted: 11 months ago
Last activity: 11 months 2 weeks ago

New JSESSIONID for every server request of single user session

Hi All,

We have noticed that Pega is generating new JSESSION ID and Pega-RULES for every single server request from a Pega web browser of a single user session hence causing session affinity issue. This issue is only when we are connecting to Tomcat server through Webseal junction,

We don't have any load-balancer.

We are not facing this problem if we are connecting directly to tomcat server through browser.

Below are my observations

First Interaction with server after login

Thread 1

JsessionID -- 60512255CBF4C31892083630DC82F74C

Pega Rules -- HA1A437DAE32C727899C6B6D56411D15A

Thread 2

JsessionID -- 60512255CBF4C31892083630DC82F74C

Pega Rules -- HA1A437DAE32C727899C6B6D56411D15A

Thread 3

JsessionID -- 60512255CBF4C31892083630DC82F74C

Pega Rules -- HA1A437DAE32C727899C6B6D56411D15A

Second Interaction with server

Thread 1

JsessionID -- 60512255CBF4C31892083630DC82F74C

Pega Rules -- HA1A437DAE32C727899C6B6D56411D15A

Thread 2

JsessionID -- 588D44A00389C410181B58EC1C2B0904

Pega Rules -- HDA9F680A7F0FCBD7A61F5F6BDDB50495

Thread 3

JsessionID -- 588D44A00389C410181B58EC1C2B0904

Pega Rules -- HDA9F680A7F0FCBD7A61F5F6BDDB50495

Pega Platform System Administration Low-Code App Development Installation and Deployment
Share this page LinkedIn