[NETCONF-20] netconf client didnot reconnect when netconf server close session Created: 18/Mar/15  Updated: 15/Mar/19  Resolved: 24/Nov/15

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Bo Li Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Text File log.txt    
Issue Links:
Blocks
blocks CONTROLLER-670 Milestone: Integration of Sal Netconf... Resolved
External issue ID: 2863

 Description   

I have a netconf server which defined a timeout if no netconf request in specific time, netconf server will be send close request to ODL.

but if I use following to check the status
GET http://localhost:8181/restconf/operational/opendaylight-inventory:nodes/

it is still Conntected.
<netconf-node-inventoryConnected>true</netconf-node-inventoryConnected>

If I send a request to netconf server, it will be failed. need restart the ODL to reconnect the ipos server.

 Comments   
Comment by Maros Marsalek [ 19/Mar/15 ]

This happens also for the loopback netconf connection and I believe it worked fine. Could you provide the log from your run ?

Comment by Maros Marsalek [ 19/Mar/15 ]

Tested today using current master branch with loopback connection. Netconf server in ODL was set to drop connection after 1 minute idle. I left it like that for a while and each minute a disconnect and a reconnect appeared. Also tried Restconf and all the requests worked fine.

So the logs are necessary to see what the failure is with your device.

Comment by Bo Li [ 20/Mar/15 ]

1. 2015-03-20 14:38:06,474
Get operation OK
2.2015-03-20 14:43:06,595
netconf server disconnect session
3.2015-03-20 14:43:06,792
create a new session
4.2015-03-20 14:48:09,798
netconf server disconnect session
5.2015-03-20 14:52:27,041
Get failed by java.nio.channels.ClosedChannelException

Comment by Bo Li [ 20/Mar/15 ]

Attachment log.txt has been added with description: ODL client reconnection log

Comment by Maros Marsalek [ 20/Mar/15 ]

Thanks for the log. I was trying to reproduce this issue with no success so I have a couple of questions:

  • What exact version of ODL are you using (if master then I am interested in last commit you are on) ?
  • What is your netconf server ? is there any chance I could debug ODL when connecting to your server ?
  • What changes (if any) did you do to the code in ODL ? Could I see them ?
Comment by Bo Li [ 20/Mar/15 ]

(In reply to Maros Marsalek from comment #4)
> Thanks for the log. I was trying to reproduce this issue with no success so
> I have a couple of questions:
>
> - What exact version of ODL are you using (if master then I am interested in
> last commit you are on) ?
I'm using the helium.
Tag: release/helium-sr2

> - What is your netconf server ? is there any chance I could debug ODL when
> connecting to your server ?

My netconf server is Ericsson private one. I don't think you can connect it in my company. You can tell me which information you need, and I can fetch them.

> - What changes (if any) did you do to the code in ODL ? Could I see them ?
The only change before this issues is to make base 1.1 capability more specific.

Comment by Bo Li [ 23/Mar/15 ]

Hi Maros,

Could you tell where I can find netconf client reconnect the netconf server after session closed?

Comment by Maros Marsalek [ 26/Mar/15 ]

Please take this bug if you are working on it. If no, we will take a look at this.

Comment by Bo Li [ 31/Mar/15 ]

Hi Maros,

I'm not working on it, please take a look at by you. I can provide supports on it.

Thanks

Comment by Maros Marsalek [ 22/Apr/15 ]

Moving to Helium-4 target as this was detected on Helium-SR2

Comment by Robert Varga [ 13/Nov/15 ]

Move to NETCONFI project.

Comment by Tomas Cere [ 24/Nov/15 ]

We were unable to reproduce this.
Please open a new bug if the issue is still present in Lithium/Berylium.

Generated at Wed Feb 07 20:13:58 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.