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-125 netconf <p>Netconf should timeout connection that is not established after specified time in connection-timeout-millis and then should try to reconnect connection according to reconnecting strategy (obeying other connection parameters like max-connection-attempts etc.) </p> <p>Now, if netconf tries to connect to a device that does not adverties hello message, netconf tiemouts after the specified time but does not cancel established SSH session and immediately tries to establish new connection, ignoring delays between connections and maximum connection attempts.</p> <p>If netconf tries to establish ssh session with device with slow ssh server implementation (simulated by TCP server), it does not timeout after specified time at all.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-125

connection-timeout-milliseconds parameter is not working properly for ssh connections

Bug Resolved Done Sarguna Dharani Jakub Morvay Wed, 13 Jan 2016 14:58:20 +0000 Wed, 12 May 2021 08:12:01 +0000 Mon, 16 Mar 2020 11:50:41 +0000 Magnesium SR1 Aluminium Sodium SR3 netconf 0 3 <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga" class="user-hover" rel="rovarga">rovarga</a>, when I see a ticket like this that was marked 'in review' -&gt; 'resolved' but don't see any gerrit or comment to understand<br/> why, what is the likely reason? For this it seems like a really old ticket from 2016 about a pretty basic bug (connection retry not working<br/> after timeout value is hit), I am assuming we are closing because we know it got fixed at some point. Let me know if it's something<br/> different.</p> Development External issue ID 4954 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01wlz: