ICEpush
  1. ICEpush
  2. PUSH-257

Cloud Push duplication

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.3
          • Fix Version/s: EE-3.3.0.GA
          • Component/s: Push Library
          • Labels:
            None
          • Environment:
            ICEmobile, ICEpush cloud push

            Description

            Jun 21, 2013 10:17:52 PM com.icesoft.icepush.APNSNotificationProvider send
            FINE: APNSNotificationProvider.send apns:78a89442633ebff189cee982e64a45ff138
            Jun 21, 2013 10:17:53 PM com.icesoft.icepush.APNSNotificationProvider send
            FINE: APNSNotificationProvider.send apns:78a89442633ebff189cee982e64a45ff138
            Jun 21, 2013 10:17:54 PM com.icesoft.icepush.APNSNotificationProvider send
            FINE: APNSNotificationProvider.send apns:78a89442633ebff189cee982e64a45ff138

              Activity

              Ascending order - Click to sort in descending order
              Ted Goddard created issue -
              Ted Goddard made changes -
              Field Original Value New Value
              Assignee Jack Van Ooststroom [ jack.van.ooststroom ]
              Hide
              Permalink
              Ted Goddard added a comment -

              This is likely due to the same Cloud Push being sent for each push ID.

              Show
              Ted Goddard added a comment - This is likely due to the same Cloud Push being sent for each push ID.
              Jack Van Ooststroom made changes -
              Status Open [ 1 ] In Progress [ 3 ]
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              Sending icepush-ee/core/src/main/java/org/icepush/BlockingConnectionServer.java
              Sending icepush-ee/core/src/main/java/org/icepush/LocalPushGroupManager.java
              Transmitting file data ..
              Committed revision 36356.

              Show
              Jack Van Ooststroom added a comment - Sending icepush-ee/core/src/main/java/org/icepush/BlockingConnectionServer.java Sending icepush-ee/core/src/main/java/org/icepush/LocalPushGroupManager.java Transmitting file data .. Committed revision 36356.
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #36356 Mon Jun 24 18:08:50 MDT 2013 jack.van.ooststroom Fixed JIRA PUSH-257 : Cloud Push duplication
              Files Changed
              Commit graph MODIFY /icepush/trunk/icepush/core/src/main/java/org/icepush/LocalPushGroupManager.java
              Commit graph MODIFY /icepush/trunk/icepush/core/src/main/java/org/icepush/BlockingConnectionServer.java
              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              When reloading the page a new PushID is created, and the old PushID(s) are still part of the listen.icepush requests. In addition all PushIDs are still part of the same Group. Due to the lack of a BrowserID class representation at the server side at the moment, a ConfirmationTimeout TimerTask was being scheduled for every PushID in the Group, regardless of if multiple PushIDs belong to the same BrowserID. There can be up to a single NotifyBackURI per BrowserID. Each PushID can have up to a single associated NotifyBackURI. When iterating over the PushIDs of a Group it will keep track of if a particular NotifyBackURI already has its ConfirmationTimeout TimerTask scheduled. If not, schedule it, otherwise skip it. Marking this one as FIXED.

              Show
              Jack Van Ooststroom added a comment - When reloading the page a new PushID is created, and the old PushID(s) are still part of the listen.icepush requests. In addition all PushIDs are still part of the same Group. Due to the lack of a BrowserID class representation at the server side at the moment, a ConfirmationTimeout TimerTask was being scheduled for every PushID in the Group, regardless of if multiple PushIDs belong to the same BrowserID. There can be up to a single NotifyBackURI per BrowserID. Each PushID can have up to a single associated NotifyBackURI. When iterating over the PushIDs of a Group it will keep track of if a particular NotifyBackURI already has its ConfirmationTimeout TimerTask scheduled. If not, schedule it, otherwise skip it. Marking this one as FIXED.
              Jack Van Ooststroom made changes -
              Status In Progress [ 3 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  Jack Van Ooststroom
                  Reporter:
                  Ted Goddard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: