Announcement Announcement Module
Collapse
No announcement yet.
Issue when deploying on multiple app server (load-balanced). Sticky session needed? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Issue when deploying on multiple app server (load-balanced). Sticky session needed?

    We're trying to deploy our spring-security-oauth2 provider on multiple instances of glassfish (behind a load balancer).

    It was working just alright when using just one instance (test enviroment situation) but it fails on the multiple instances one.

    It would appear that for the whole flow to go alright some part of the session is stored in the app server so then all other requests would have to be done the same instance (sticky stuff).

    If anybody could clarify this part, it would be much appreciated.

  • #2
    Correct. We use the SessionAttributeStorage abstraction from Spring MVC, so by default it uses HttpSession. Sticky sessions would work.

    Comment


    • #3
      I would prefer NOT to use sticky sessions. Is this possible?

      Comment


      • #4
        Yes. You can use a custom SessionAttributeStorage (that's what it's for.) If I were you I would go with sticky sessions - it's a lot easier.

        Comment

        Working...
        X