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-226 netconf <p>When we uses sal-netconf-connector(Lithium sr4) to connet our router device(contains 200+ yang capabilities),it costs hours to be connected. The conntroller does not support the most yang capabilities of the device, but it is blocked in </p> <p> at com.google.common.util.concurrent.Futures$6.run(Futures.java:1310)<br/> at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)<br/> at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)<br/> at com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)<br/> at com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)<br/> at com.google.common.util.concurrent.ForwardingListenableFuture.addListener(ForwardingListenableFuture.java:47)<br/> at com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)<br/> at com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258)<br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$RecursiveSchemaSetup.setUpSchema(NetconfDevice.java:460)<br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$RecursiveSchemaSetup.access$1400(NetconfDevice.java:390)<br/> at org.opendaylight.controller.sal.connect.netconf.NetconfDevice$RecursiveSchemaSetup$1.onFailure(NetconfDevice.java:443)</p> <p>it costs too many hours untill it connected at last with many source miss yang capabilities.</p> <p>Operating System: Linux<br/> Platform: PC</p> NETCONF-226

Use sal-netconf-connector to connet device costs too much time

Bug Resolved Done Unassigned Hou Jin Sat, 16 Jul 2016 11:26:30 +0000 Fri, 15 Mar 2019 22:22:26 +0000 Fri, 19 Aug 2016 06:41:04 +0000 netconf 0 5 <p>Hi,</p> <p>Unfortunately, Lithium is not supported anymore. Can you please try this on Beryllium or Boron?</p> <p>Also moving bug from controller product to netconf product here in bugzilla, since netconf is standalone project now.</p> <p>We find that when a netconf device(with 200 yang capabilities that controller does not support) connected, in function onRemoteSessionUp it costs too much time in setUpSchema. It uses a recursion to check the yang capabilities of the remote device. when found a yang capability does not supported in controller it throw a MissingSchemaSourceException and remove the yang capability and recursively setUpSchema. Each check it use Futures.allAsList to check all yang capabilities so it will result 200 MissingSchemaSourceExceptions first time and 199 MissingSchemaSourceExceptions next time and ... All the time wasted in Exceptions so it costs hours to connect the device.</p> <p>I try to fix the bug.</p> <p>Every missing source YANG capability will throw a MissingSchemaSourceException and trigger an additional call to createSchemaContext in class RecursiveSchemaSetup.</p> <p>I filter out all missing source YANG capabilities before call createSchemaContext, in order to avoid repeated call createSchemaContext too many times.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/42133/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/42133/</a></p> Development External issue ID 6198 External issue URL Issue Type Rank 0|i01x8f: