[CONTROLLER-471] RpcInvocationStrategies in BindingIndependentConnector have inconsistent behavior Created: 14/May/14 Updated: 27/May/14 Resolved: 27/May/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Devin Avery | Assignee: | Devin Avery |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| External issue ID: | 1009 |
| Description |
|
The RpcInvocationStrategies in the BindingIndependentConnect have inconsistent and what appears to be incorrect behavior. For example, the NoInputNotOutput class simple returns a null future in the forward to dom broker method without actually invoking anything! Additionally the methods inconsistently pass errors back to the caller, and the success state is lost if non-null. This bug will be used to select and perform consistent actions in all cases. |
| Comments |
| Comment by Devin Avery [ 14/May/14 ] |
|
To test - invoke the toaster:make-toast method 2 times back to back (with a doneness of 10). Notice how the second call returns success, even though the toaster is suppose to return a failure if the make toast is already in progress. |
| Comment by Devin Avery [ 27/May/14 ] |
|
Code completed and merged: https://git.opendaylight.org/gerrit/#/c/6906/ |