[CONTROLLER-1049] Clustering : Operation is timeout when invoking remote routed rpc Created: 28/Nov/14 Updated: 19/Oct/17 Resolved: 30/Dec/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Xin Chang | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 2449 |
| Description |
|
When routed rpc in model bundle loaded after odl-mdsal-clustering, remotely invoking such routed rpc always causes timeout exception. From debug level loggings, it shows that RpcBroker fails in transforming input composite node to xml due to absent of scheme context for this rpc. In RpcBroker, the property schemaContext is defined as final and initialized via RpcManager, which is further initialized via RemoteRpcProvider. It is obvious that all model bundles loaded after sal-remoterpc-connector can not push schemes to RpcBroker. |
| Comments |
| Comment by Xin Chang [ 28/Nov/14 ] |
|
Attachment karaf.log has been added with description: The logging file for reported bug |
| Comment by Xin Chang [ 28/Nov/14 ] |
|
| Comment by Xin Chang [ 29/Nov/14 ] |
|
Attachment karaf_Nov_29.log has been added with description: The latest log (29th Nov) for reported bug |
| Comment by George Zhao [ 04/Dec/14 ] |
|
fix in this change |