[CONTROLLER-1145] Improve wrong response handling in sal-netconf-connector Created: 10/Feb/15 Updated: 24/Feb/15 Resolved: 24/Feb/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | netconf |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Maros Marsalek | Assignee: | Marian Dubai |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
If netconf connector detects invalid response (e.g. one response in a sequence gets lost or 2 responses from device come in wrong order), the netconf connector keeps waiting on the same requests and keeps throwing incomming responses away. This makes the connector unusable until restart. Make the connector try to find proper request to invalid message by skipping waiting requests. Worst case scenario with this improvement is that all waiting requests will be removed and marked as failed, but the connector itself would continue to work. |
| Comments |
| Comment by Maros Marsalek [ 24/Feb/15 ] |