Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-2722

RequestCycle.detach() recreates SessionData after logout

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Invalid
    • Affects Version/s: 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.4.10, 1.4.11
    • Fix Version/s: None
    • Component/s: wicket
    • Environment:
      Wicket 1.4.6, Spring 2.5.6, Hibernate 3.3.1-GA, AspectJ 1.6.8, Eclipse 3.5.2, Windows 7 32bit

      Description

      After every page request the RequestCycle asks the RequestLogger (if any) to write the time taken etc to the logger (using the SessionData of the current Session). If none exists then a new SessionData is created (RequestLogger line 250). However when a user logs out the SessionData is destroyed, but the page still has to detach and thus creates a new SessionData entity.

      When we lookup the live sessions and peak sessions from RequestLogger, the two numbers are (nearly) always the same. Which is wrong when all users have logged out or closed their browser (no difference there).

        Attachments

        1. req-logger.patch
          1 kB
          Peter Ertl

          Activity

            People

            • Assignee:
              ivaynberg Igor Vaynberg
              Reporter:
              hielkehoeve Hielke Hoeve
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: