Wicket
  1. Wicket
  2. WICKET-3668

Session.getPageMaps is not thread safe.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.17
    • Fix Version/s: 1.4.18
    • Component/s: wicket
    • Labels:

      Description

      Session.getPageMaps first gets all attributes names, then it add all pageMaps with a name of a pageMap.

      But another thread with the same session might remove the attribute in the time between the get attribues names and the get of the attribute.
      So the result will include a null object that will throw null pointer in the sort.

      The senario is basicly related to previous bug where pageMap was created for link with popup (So pageMap would exceed max level and massive removal of pageMaps).
      But this could still happen, and should be easy to fix (Just don't add a null pageMap to the list)...

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Igor Vaynberg
            Reporter:
            Yaron
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1h
              1h
              Remaining:
              Remaining Estimate - 1h
              1h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development