Details

    Description

      This basically a redo for LPS-26931's issue.

      The original design for PortletSessionTracker was wrong, and LPS-26931 made it even more complex.

      Servlet Spec 7.3 "Session Scope" says, when across web applications, a HttpSession boundary must be setup, although the HttpSession's id remains the same, all the data is isolated to its own web application scope, this boundary is required to avoid classloading issues.

      As a result, when delegating page rendering from portal to WAR portlets, we creates new portlets web app scope HttpSession objects, which share the same portal HttpSession id.
      To properly track them, we need to group them by HttpSession id, tag each tracked HttpSession object by servlet contextPath, this will ensure we track all portlets' sessions, and we track each object exactly once.

      Attachments

        Issue Links

          Activity

            People

              brian.chan Brian Chan
              shuyang.zhou Shuyang Zhou
              Kiyoshi Lee Kiyoshi Lee
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                8 years, 47 weeks, 3 days ago

                Packages

                  Version Package
                  6.1.X EE
                  6.2.1 CE GA2
                  6.2.X EE