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
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
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.
Thanks in
Hi Team
1. We have a RoutedRpc registered on one of the clustered nodes using
ClusterSingletonService.
2. ClusterSingletonService is up and is shown available on member-2 (verified
-> http://{{ipaddr}}:8181/restconf/operational/entity-owners:entity-owners)
3. While invoking API on registered
On 04/03/2019 13:37, Vikram Darsi wrote:
> Hi Team
Hello,
> 1. We have a RoutedRpc registered on one of the clustered nodes using
> ClusterSingletonService.
>
> 2. ClusterSingletonService is up and is shown available on member-2
> (verified ->
>
