[CONTROLLER-824] DOMDataBrokerTransactionChainImpl: wrong shutdown sequencing Created: 12/Sep/14 Updated: 17/Oct/14 Resolved: 17/Oct/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| 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: | 1845 |
| Description |
|
DOMDataBrokerTransactionChainImpl.close() does not correctly wait for all transactions to complete before emitting successful close callback. There seems to be a larger lifecycle issue, which makes it unclear how a transaction failure interacts with close(). |
| Comments |
| Comment by Robert Varga [ 13/Sep/14 ] |
|
It seems that the problem runs a bit deeper, too, as the datastore needs updating too. Retargetting to RC2. |
| Comment by Robert Varga [ 18/Sep/14 ] |