[NETCONF-409] Existing Websocket notifications missing if there is any delay between subscription and connection Created: 25/Apr/17 Updated: 15/Mar/19 Resolved: 01/Jun/17 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Ritu Sood | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 8299 | ||||||||
| Description |
|
If there is a delay in between the subscription and the actual connection of the websocket there are no notification send for existing nodes. i.e between steps 2 and 3 in this page: The connection has to be immediate after subscription otherwise the notifications are lost. |
| Comments |
| Comment by Robert Varga [ 01/Jun/17 ] |
|
The problem here is that the change listener is created immediately when the stream is defined and therefore it is going to lose some events from its buffer (if there is even one). The alternative solution proposed in NETCONF-351 will naturally solve this particular issue, as the change listener will be creater for each websocket connection (and tied to it), hence the race window will no longer exist. Closing this issue down as a duplicate, as the fix for NETCONF-351 will also address this one. |