[OPNFLWJAVA-75] When closing OutboundQueue close() should go prior to finishShutdown() Created: 31/Mar/16 Updated: 07/Jun/16 Resolved: 07/Jun/16 |
|
| Status: | Resolved |
| Project: | openflowjava |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michal Rehak | Assignee: | Abbas P Pareedkunju |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 5637 |
| Priority: | Normal |
| Description |
|
When device disconnects with outstanding entries in queue segment it could occur that entry.commit() gets invoked between segment.failAll() and OutboundQueueProvider.close(). Effectively there can be entries with untouched callback but in state committed. And then callback will never finish underlying rpc future object. |
| Comments |
| Comment by Abbas P Pareedkunju [ 02/Jun/16 ] |
|
Hi Michal, The below patch is submitted for review, request to please review and give update the score. https://git.opendaylight.org/gerrit/#/c/39746/ Thanks, |