ICEpush
  1. ICEpush
  2. PUSH-123

Implement PushId expiration mechanism

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.1
    • Component/s: Push Library
    • Labels:
      None
    • Environment:
      server
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.)

      Description

      We need to implement expiry mechanism for PushIds so they an be expired independently from the groups they belong to.

        Activity

        Hide
        Mircea Toma added a comment -

        Implemented pushId expiry mechanism. Introduced internal PushID class meant to keep track of the last access time and the groups the pushId belongs to. Refactored code to iterate safely over shared collections. Also the map lookups are changed to avoid any NPE exceptions caused by concurrent accesses.

        Show
        Mircea Toma added a comment - Implemented pushId expiry mechanism. Introduced internal PushID class meant to keep track of the last access time and the groups the pushId belongs to. Refactored code to iterate safely over shared collections. Also the map lookups are changed to avoid any NPE exceptions caused by concurrent accesses.
        Hide
        Mircea Toma added a comment -

        The pushId expiry interval can be changed by using 'org.icepush.pushIdTimeout'. The default value is 120,000 ms (2 minutes).

        Show
        Mircea Toma added a comment - The pushId expiry interval can be changed by using 'org.icepush.pushIdTimeout'. The default value is 120,000 ms (2 minutes).

          People

          • Assignee:
            Unassigned
            Reporter:
            Mircea Toma
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: