Announcement Announcement Module
No announcement yet.
Cluster-aware SessionRegistry for concurrent logins? Page Title Module
Move Remove Collapse
This topic is closed
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Hmmm...MUCH more complex than simply doing

    <security:http auto-config="false" entry-point-ref="digestProcessingFilterEntryPoint">

    Why doesn't this work? Because I don't have auto-config on?


    • #17
      The issue seems to be that when one of the nodes of the cluster are gracefully shutdown, the HTTPSessionDestroyedEvent will be fired off for every session that belongs to that node, even if other nodes are available in the session. From what I read this is a common problem with clustering and webservers such as JBoss, Tomcat, and Oracle Application Server. Currently the only solution I found was to load a properties file on the HTTPSessionDestroyedEvent and check to see if a shutdown is occurring or not. The drawback to this is that the system admin has to remember to update the properties file before and after shutdown. I am interested in more solutions.


      • #18
        Why do you have concurrent session filter as the first filter?

        Is that because of the environment you're running in? (load balanced/clustered)

        Or is it because of the way the session filter works? It seems that out of the box, the concurrent session filter is one of the last filters in the chain.