https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-409 netconf <p>If there is a delay in between the subscription and the actual connection of the websocket there are no notification send for existing nodes.</p> <p>i.e between steps 2 and 3 in this page:<br/> <a href="https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Restconf:Netconf_event_notification_subscription" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Restconf:Netconf_event_notification_subscription</a></p> <p>The connection has to be immediate after subscription otherwise the notifications are lost.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-409

Existing Websocket notifications missing if there is any delay between subscription and connection

Bug Resolved Duplicate Unassigned Ritu Sood Tue, 25 Apr 2017 16:34:40 +0000 Fri, 15 Mar 2019 22:22:40 +0000 Thu, 1 Jun 2017 21:17:19 +0000 restconf-nb 0 1 <p>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).</p> <p>The alternative solution proposed in <a href="https://jira.opendaylight.org/browse/NETCONF-351" title="Websocket implementation doesn&#39;t support unsubscribe for notifications" class="issue-link" data-issue-key="NETCONF-351">NETCONF-351</a> 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.</p> <p>Closing this issue down as a duplicate, as the fix for <a href="https://jira.opendaylight.org/browse/NETCONF-351" title="Websocket implementation doesn&#39;t support unsubscribe for notifications" class="issue-link" data-issue-key="NETCONF-351">NETCONF-351</a> will also address this one.</p> Duplicate NETCONF-351 Development External issue ID 8299 External issue URL Issue Type Rank 0|i01yd3: