[CONTROLLER-626] Netconf negotiation failure does not close channel properly if data is still being transfered Created: 15/Jul/14 Updated: 25/Jul/23 Due: 18/Jul/14 Resolved: 18/Jul/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Maros Marsalek | Assignee: | Maros Marsalek |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| External issue ID: | 1365 |
| Description |
|
If Netconf client negotiatior marks the session a failure and closes the channel, the traffic over network is not terminated and continues infinitely. Investigate how to properly close the channel and terminate all traffic in netconf negotiator. Probably a server side issue as well. |
| Comments |
| Comment by Maros Marsalek [ 16/Jul/14 ] |
|
The channel is closed properly, but it waits for current message to be transfered. To interrupt the transfer, it would require to shutdown the netty eventLoopGroup. Only submitted a check to log whether the channel was closed properly or not. |