https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1397 controller <p>I am in the process of trying to get IT testing working in the startup archetype.</p> <p>In the process of doing that, I am getting IT test failures with an exception:</p> <p>Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 477.459 sec &lt;&lt;&lt; FAILURE! - in HelloIT<br/> testRPC(HelloIT) Time elapsed: 394.96 sec &lt;&lt;&lt; ERROR!<br/> org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath</p> {path=[(urn:opendaylight:params:xml:ns:yang:hello?revision=2015-01-05)hello-world]} <p> available<br/> at org.opendaylight.controller.md.sal.dom.broker.impl.DOMRpcRoutingTable.invokeRpc(DOMRpcRoutingTable.java:183)<br/> at org.opendaylight.controller.md.sal.dom.broker.impl.DOMRpcRouter.invokeRpc(DOMRpcRouter.java:124)<br/> at org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter.invoke0(RpcServiceAdapter.java:64)<br/> at org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter.access$000(RpcServiceAdapter.java:42)<br/> at org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter$RpcInvocationStrategy.invoke(RpcServiceAdapter.java:156)<br/> at org.opendaylight.controller.md.sal.binding.impl.RpcServiceAdapter.invoke(RpcServiceAdapter.java:95)<br/> at com.sun.proxy.$Proxy84.helloWorld(Unknown Source)<br/> at HelloIT.testRPC(HelloIT.java:57)</p> <p>This happens in <b>spite</b> of the fact that if I put a debugger breakpoint on HelloIT.java:56 (the line before the exception is thrown) I can successfully access the RPC via Restconf.</p> <p>The RPC implementation is registered with the BindingAwareBroker via the ProviderContext, and we are attempting to access if in the IT test via the BindingAwareBroker via a ProviderContext. But it appears that the BindingAwareBroker is forwarding it to the DomBroker where the RPC is not being found.</p> <p>If we try to access it via RestConf however its being access correctly.</p> <p>To recreate:</p> <p>As part of doing that, I am using this patch:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/16294/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/16294/</a></p> <p>to do IT testing via a parent and base classes, so you will need to build the new directories from there.</p> <p>You will find attached a hello.zip file which contains the code I am working from. Building hello/ will build hello/it which will run the IT tests and fail appropriately.</p> <p>The POSTMAN to use RESTCONF is here: <a href="https://www.getpostman.com/collections/fe835cc9c7b50343f752" class="external-link" target="_blank" rel="nofollow noopener">https://www.getpostman.com/collections/fe835cc9c7b50343f752</a></p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1397

BindingAwareBroker has issues invoking BindingAware RPCs

Bug Resolved Cannot Reproduce Unassigned Ed Warnicke Fri, 24 Jul 2015 00:42:50 +0000 Thu, 19 Oct 2017 21:29:03 +0000 Mon, 3 Aug 2015 11:53:40 +0000 Beryllium mdsal 0 1 <p>Attachment hello.zip has been added with description: hello.zip</p> <p>Further note on recreation:</p> <p>cd hello/it<br/> mvn clean install -Dkaraf.debug</p> <p>Will cause the karaf instance for the integration test to run in debug mode on port 5005, which can be handy.</p> <p>What I think I've found via investigation using the debugger:</p> <p>When I debug HelloIT.testRPC(): I see from:</p> <p>HelloService service = getSession().getRpcService(HelloService.class);</p> <p>That the service I am getting back has as its delegate something of type DOMRpcRouter (and note: a different instance than the one I see in the debugger coming back to Restconf). I think this tells me that BindingAwareRPCs are all being routed through the DOM Broker, even when both producer and consumer are BindingAware.</p> <p>When I drill into HelloIT:57:<br/> Future&lt;RpcResult&lt;HelloWorldOutput&gt;&gt; outputFuture = service.helloWorld(builder.build());</p> <p>RPCServiceAdapter.invoke():87 </p> <p>final RpcInvocationStrategy rpc = rpcNames.get(method);</p> <p>gives an rpc of type: RpcServiceAdapter$NonRoutedStrategy</p> <p>which after a few jumps down the stack takes us to:</p> <p>DOMRpcRoutingTable.invoke()... which has an rpcs member of type EmptyImmutableBiMap... which I believe is our problem... basically... BindingAware delegates to DOM... and for some reason DOM doesn't have the registration in the DOMRoutingTable that it has.</p> <p>Please note though... if I stick a break point in DOMRoutingTable.invoke and invoke restconf... its a different object which <b>does</b> have the HelloWorld RPC in its rpcs member.</p> <p>Which initial config are you using to replicate your problem?</p> <p>There should be one instance of DOMRpcRouter if not, I would suspect configuration problem.</p> <p>In Lithium - binding shortcut was removed - but there is no performance hit, even if DOM Broker is used data are not serialized / deserialized to DOM.</p> <p>Logs of a failed run can be found here:</p> <p><a href="http://pastebin.com/eyYxJCgL" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/eyYxJCgL</a></p> <p>Turned out test staticly binded to first Broker available. During boot-up with clustering enabled - broker is started and then replaced with newer instance.</p> <p>Test code ended using first broker for tests and applications using second test.</p> <p>Fix in test to not use pax-exam @Inject capability fixed issue.</p> Development External issue ID 4048 External issue URL Rank 0|i02qbj: