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-87 netconf <p>When creating mount point for netconf device according to <br/> <a href="https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Spawning_Additional_Netconf_Connectors_While_the_Controller_is_Running" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Spawning_Additional_Netconf_Connectors_While_the_Controller_is_Running</a></p> <p>then the default value for default-request-timeout-millis is 60k. This can be confirmed in DS/operational.</p> <p>But if I add following to the input and POST it into DS/config:<br/> &lt;max-connection-attempts xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;3&lt;/max-connection-attempts&gt;<br/> &lt;between-attempts-timeout-millis xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;2000&lt;/between-attempts-timeout-millis&gt;<br/> &lt;connection-timeout-millis xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;10000&lt;/connection-timeout-millis&gt;<br/> &lt;default-request-timeout-millis xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"&gt;10000&lt;/default-request-timeout-millis&gt;</p> <p>then it gets correctly reflected in DS/operational but it still takes 60 seconds till the connection times out and so the whole connection ends up with failure after 205 seconds.</p> <p>Is this the right parameter to control connection timeout? If not, what is the recommended way of setting up shorter connection timeout?</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-87

default-request-timeout-millis ignored for netconf device

Bug Resolved Cannot Reproduce Jakub Morvay Michal Rehak Mon, 19 Oct 2015 15:05:10 +0000 Fri, 15 Mar 2019 22:22:16 +0000 Wed, 13 Jan 2016 15:04:00 +0000 netconf 0 3 <p>I am not able to reproduce this bug. All connection related configuration parameters work for me correctly. </p> <p>I tried connecting to closed port on a device, to a device that does not advertise hello message, to a device that has a slow SSH server, but I did not encounter described behaviour. </p> <p>More detailed description of used setting is needed to reproduce this bug.</p> <p>It is really easy for me to reproduce, and here is my setup:</p> <p>I have embedded devices running confd, wired to a switch. The switch is providing the network.<br/> I put down the internet port of the switch (thus netconf devices doesn't have internet access anymore), I perform a get on a netconf device's schema, the operation will hang for a while before eventually fail.</p> <p>Using this default-request-timeout-millis should fail whatever RPCs after the desired delay, but it's not working.</p> <p>After discussion with Alexis, the bug he can reproduce is not same as this one. He opened new case for his scenario <a href="https://bugs.opendaylight.org/show_bug.cgi?id=4940" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=4940</a>.</p> Development External issue ID 4496 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01wdj: