Winstone: Memory leak due to default session timeout of -1

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Blocker
    • Component/s: core
    • Environment:
      Hudson 1.337 (Winstone), Solaris 10 SPARC, Sun JDK 1.6.0_16

      We are running Hudson with its embedded Winstone servlet engine. User authentication within Hudson is done via Hudsons LDAP security realm using our corporate ActiveDirectory via LDAP.

      After running Hudson a few weeks we're running into OutOfMemory exceptions. Here the culprit is a single winstone.WebAppConfiguration instance holding a lot of winstone.WinStoneSession instances each holding an Acegi RememberMeAuthenticationToken instance with 36k data from the authenticated users AD record.

      It seems that Hudson isn't setting Winstones session timeout. Without specifying a session timeout winstone.WebAppConfiguration.makeNewSession() is using a session timeout of -1.

            Assignee:
            Unassigned
            Reporter:
            tjuerge
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: