Jetspeed 2
  1. Jetspeed 2
  2. JS2-768

Desktop pipeline gets null page in request context

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.3
    • Fix Version/s: 2.1.3, 2.2.0
    • Component/s: Desktop
    • Labels:
      None

      Description

      When using the NTLM Security Valve, running under the desktop pipeline intermittently throws exceptions in the desktop as shown in the stack trace below
      It seems that the Page is NULL in the request context

      ERROR org.apache.jetspeed.profiler.impl.ProfilerValveImpl - Exception in
      request pipeline: null
      java.lang.NullPointerException
      at
      org.apache.jetspeed.om.page.ContentPageImpl.getId(ContentPageImpl.java:4
      69)
      at
      org.apache.jetspeed.profiler.impl.ProfilerValveImpl.getPageActionAccess(
      ProfilerValveImpl.java:310)
      at
      org.apache.jetspeed.profiler.impl.ProfilerValveImpl.invoke(ProfilerValve
      Impl.java:244)
      at

        Activity

        David Sean Taylor created issue -
        Hide
        David Sean Taylor added a comment -

        The Site session context was getting reset over the span of a page refresh from the desktop pipeline
        The problem was that the desktop pipeline uses multiple pipelines causing frequent refresh of the session context over multithreaded requests on the same session (desktop is multithreaded)
        The check to see if the pipeline changed was added to support switching between the Desktop and Portal, which is often done during evaluations but probably not a valid use case
        Introduced a new method to abstract the changing of pipelines, and only return true if the Portal Pipeline is involved, otherwise, short circuit this check

        Show
        David Sean Taylor added a comment - The Site session context was getting reset over the span of a page refresh from the desktop pipeline The problem was that the desktop pipeline uses multiple pipelines causing frequent refresh of the session context over multithreaded requests on the same session (desktop is multithreaded) The check to see if the pipeline changed was added to support switching between the Desktop and Portal, which is often done during evaluations but probably not a valid use case Introduced a new method to abstract the changing of pipelines, and only return true if the Portal Pipeline is involved, otherwise, short circuit this check
        David Sean Taylor made changes -
        Field Original Value New Value
        Fix Version/s 2.2 [ 12312318 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ate Douma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            David Sean Taylor
            Reporter:
            David Sean Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development