[OPNFLWPLUG-550] TransactionChainManager state never goes back to WORKING Created: 18/Sep/15 Updated: 27/Sep/21 Resolved: 23/Sep/15 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michal Rehak | Assignee: | Jozef Gloncak |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4328 |
| Description |
|
After first use of TransactionChainManager it gets stuck in SHUTTING_DOWN state which enables every new connection from the same device to register another readyForNewTransactionChainHandler. State of TxChainManager should change once the ownership is gained by actual connectionContext. Besides the correct cleanup mechanism should be checked and covered by tests in case of connection drop of a waiting candidate. |
| Comments |
| Comment by Michal Rehak [ 23/Sep/15 ] |
|
https://git.opendaylight.org/gerrit/27336 Actually this was not a bug. Just unclear contract and now it is covered with unit tests. |