Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.1.0.GA
-
Fix Version/s: EE-4.2.0.GA
-
Component/s: JavaScript Client
-
Labels:None
-
Environment:Tomcat 7/8, ICEfaces EE 4 r48636
-
Assignee Priority:P2
Description
The QA cloudPush application has a cloudPush registration page and 3 different colored pages that can send priority push messages.
In this scenario a user resisters cloudPush then goes to the red page to send a notification. The user then goes to the yellow page and sends a notification and leaves the browser open on the yellow page.
The red page native notification is not sent to the device, and is not updated on the red page.
The yellow page native notification is not sent to the device but the yellow page is updated.
The red page notification should have been delivered to the device.
To demonstrate use the QA Cloud push Persistence application (/registration.jsf)
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/cloudPush
Follow the steps as in the scenario but increase the message delay to 15 seconds.
In this scenario a user resisters cloudPush then goes to the red page to send a notification. The user then goes to the yellow page and sends a notification and leaves the browser open on the yellow page.
The red page native notification is not sent to the device, and is not updated on the red page.
The yellow page native notification is not sent to the device but the yellow page is updated.
The red page notification should have been delivered to the device.
To demonstrate use the QA Cloud push Persistence application (/registration.jsf)
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/cloudPush
Follow the steps as in the scenario but increase the message delay to 15 seconds.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | mobi:cloudPush notification is not received if sending priority push from more than one page. | mobi:cloudPush notification triggered from another page is not sent if user is viewing another page with push enabled. |
| Assignee | Jack Van Ooststroom [ jack.van.ooststroom ] | |
| Fix Version/s | EE-4.1.0.GA [ 12172 ] | |
| Affects Version/s | EE-4.1.0.GA [ 12172 ] | |
| Affects Version/s | 4.1 [ 11570 ] | |
| Assignee Priority | P2 [ 10011 ] |
| Summary | mobi:cloudPush notification triggered from another page is not sent if user is viewing another page with push enabled. | mobi:cloudPush notification triggered from a page is not sent if user is viewing another page with push enabled. |
| Fix Version/s | EE-4.1.1.BETA [ 13077 ] | |
| Fix Version/s | EE-4.1.0.GA [ 12172 ] |
| Fix Version/s | EE-4.1.1.GA [ 13078 ] | |
| Fix Version/s | EE-4.1.1.BETA [ 13077 ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #48860 | Fri May 27 12:32:52 MDT 2016 | jack.van.ooststroom | Fixed JIRA |
| Files Changed | ||||
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/InternalPushGroupManager.java
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/Browser.java
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/LocalPushGroupManager.java
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/Group.java
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/ConfirmationTimeout.java
|
A fair bit of changes were required in order to get this scenario working:
- Avoid having multiple Push-IDs belonging to the same Browser-ID within the same Group. (This will need more work to support your suggested scenario of having two tabs open to the same color page.)
- Cancelling Confirmation Timeouts based on the Push-IDs send along with the listen.icepush request instead of based on the Browser-ID.
- Change usages of starting and stopping Confirmation Timeouts accordingly.
- Update the internal logic of the Confirmation Timeout to follow the new strategy.
Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - A fair bit of changes were required in order to get this scenario working:
Avoid having multiple Push-IDs belonging to the same Browser-ID within the same Group. (This will need more work to support your suggested scenario of having two tabs open to the same color page.)
Cancelling Confirmation Timeouts based on the Push-IDs send along with the listen.icepush request instead of based on the Browser-ID.
Change usages of starting and stopping Confirmation Timeouts accordingly.
Update the internal logic of the Confirmation Timeout to follow the new strategy.
Marking this one as FIXED.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | EE-4.2.0.GA [ 13074 ] | |
| Fix Version/s | EE-4.1.1.GA [ 13078 ] |
Sending icepush-ee/core/src/main/java/org/icepush/Browser.java
Sending icepush-ee/core/src/main/java/org/icepush/ConfirmationTimeout.java
Sending icepush-ee/core/src/main/java/org/icepush/Group.java
Sending icepush-ee/core/src/main/java/org/icepush/InternalPushGroupManager.java
Sending icepush-ee/core/src/main/java/org/icepush/LocalPushGroupManager.java
Transmitting file data .....
Committed revision 48860.
Sending icepush-ee/eps/src/main/java/com/icesoft/push/Browser.java
Sending icepush-ee/eps/src/main/java/com/icesoft/push/ConfirmationTimeout.java
Sending icepush-ee/eps/src/main/java/com/icesoft/push/DynamicPushGroupManager.java
Sending icepush-ee/eps/src/main/java/com/icesoft/push/InternalPushGroupManager.java
Sending icepush-ee/eps/src/main/java/com/icesoft/push/LocalPushGroupManager.java
Sending icepush-ee/eps/src/main/java/com/icesoft/push/RemotePushGroupManager.java
Sending icepush-ee/eps/src/main/java/com/icesoft/push/StatusManager.java
Transmitting file data .......
Committed revision 45139.