Hi,
We are using spring boot camunda embedded engine, when we increase the pod 2(Conatiner 2). User is not able to login we are getting 401 status code.
But when decrease to 1 pod, then user can able to login. Could you please help me on this. Do we need any config changes to scale up?
Regards,
Tiru
Hello my dear!
User session information may be being stored in memory within the Pod, and when you increase that to 2 Pods, requests may “bump” into a different Pod causing this issue.
Check with your DevOps team to use some shared session strategy or an external database that will work well no matter how many Pods you have.
Regards.
William Robert Alves
here is some background information about the login behavior of the web application in a clustered environment: Architecture Overview | docs.camunda.org
You have to configure a sticky session in the load balancer.
This blog post describes an alternative using memcache: https://camunda.com/blog/2019/06/camunda-bpm-with-session-manager
Hope this helps, Ingo