All geek questions in one place

HTTP session in load balancer

We have two servers for load balancing. Sometimes we get an invalid session after successfully logging into our application, and the user session has expired even if the session timeout is set to 30 minutes. We are not sure whether authentication occurs on one of the servers, and a subsequent request is sent to the other server. This seems random and does not happen to all users.

A noticeable invalid session only occurs on the selected network. Our app is available in 21 different stores across India. Out of 7 stores there is this problem, even in all stores using the Airtel network. Our application works great on my office network and Airtel data card. But faced with a strange problem when connecting via Jio network in my laptop. How does this happen on the Jio network?

Language: Java

Framework: Spring

Server: Jboss 7.1.1
+4
source share
1 answer

As you said, the problem is most likely due to the fact that the session is created on one server, but some of the subsequent requests go to another server that does not have the correct attributes for the session, and therefore, it considers that the user is not signed.

, , ( ). , , . , user2 B. ( ) .

. Spring . (, Spring config), , , , .

, , , :

http://blog.haproxy.com/2012/03/29/load-balancing-affinity-persistence-sticky-sessions-what-you-need-to-know/

https://touk.pl/blog/2016/03/22/haproxy-sticky-sessions-for-soap-payloads/

http://docs.spring.io/spring-session/docs/current/reference/html5/

+6

Source: https://habr.com/ru/post/1663319/

More articles:


All Articles