Hi Robert Thanks for the reply.
If it is new RpcRegistration request, understand there could be a bug in gossiping the information to the remote nodes and hence the exception. But in my case, the RpcRegistrations were successful and the routing entries are in synch in all the nodes (since rpc requests from all the nodes were successful). After some time in one of the nodes the rpc request started failing by throwing the exception. Was this kind of behaviour observed in earlier releases of ODL and subsequently addressed in Carbon? Regards Vikram -----Original Message----- From: Robert Varga <n...@hq.sk> Sent: Tuesday, March 5, 2019 2:33 PM To: Vikram Darsi <vda...@advaoptical.com>; controller-dev@lists.opendaylight.org Subject: Re: DOMRpcImplementationNotAvailableException On 04/03/2019 14:22, Vikram Darsi wrote: > Hi Robert > > We are using Boron-SR4 (Pretty old ☹), here is the exception: > https://pastebin.com/REP0ZuSx, Will the DOMRpcRouter/table on the problematic > node will eventually get updated with the missed RPCRegistration events? From > the logs it did not happen event after a long time. It should, but there have been bugs in that area of code, which were rectified by a rather thorough rewrite in Carbon. Regards, Robert _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
