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-139 netconf <p>While fixing the issue where a Netconf device was unable to handle empty list merges, we are catching the generic RuntimeException in BrokerFacace.java since there was no clarity on all possible exceptions thrown from the underlying broker. This fixes the issue but it is better to understand the exceptions thrown by NETCONF and catch specific exceptions. Alternatively we can make the NETCONF broker to throw specific exception during merge operations and catch it.<br/> This bug is file for the purposes of refactoring this part of the code.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-139

In BrokerFacade figure out and catch specific Netconf Runtime Exceptions Instead of generic RuntimeException during merge operations.

Bug Confirmed Unresolved Unassigned Balaji Varadaraju Wed, 3 Feb 2016 00:14:42 +0000 Tue, 13 Aug 2019 07:38:38 +0000 restconf-nb 0 1 <p><a href="https://github.com/opendaylight/netconf/blob/d3ca79c031339f35df362887dde8d4f54c82cfa3/opendaylight/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/sal/tx/AbstractWriteTx.java#L135-L138" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/netconf/blob/d3ca79c031339f35df362887dde8d4f54c82cfa3/opendaylight/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/sal/tx/AbstractWriteTx.java#L135-L138</a></p> <p>Netconf throws NetconfDocumentedException from the editConfig() but it gets caught and indeed a RuntimeException is rethrown, so a specific exception would need to be added to the interface.</p> Development External issue ID 5197 External issue URL Rank 0|i01wp3: