Wicket
  1. Wicket
  2. WICKET-5390

Session management doesn't work with Jetty's JDBCSessionManager

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.11.0
    • Fix Version/s: 6.12.0, 7.0.0-M1
    • Component/s: wicket
    • Labels:
      None

      Description

      I use JDBCSessionIdManager/JDBCSessionManager from Jetty to store my sessions in a DB. Jetty tries to be smart and determines if a session is dirty and only persists it then. The logic is that a call to HttpSession#setAttribute may cause the dirty flag to be set if A) the value is new OR B) the value is changed, i.e. not #equals to the previous value. Wicket stores a PageStoreManager$SessionEntry as an attribute. This class doesn't have a specific equals implementation and so from the Jetty point of view the session never changes. The effect is that after Jetty restores the session from the DB it will be always in the initial state.

      One possible fix is to always return false in SessionEntry#equals. But I'm not sure what Jetty is doing here is correct either.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Martin Grigorov
              Reporter:
              Christoph Leiter
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development