NamedEndpoint V2Listener not found in the address '{"Endpoints":{"V2_1Listener":"....

[tbertenshaw]

Describe the bug
When trying to get ActorInformation using an ActorServiceProxy for an actor which is using Remoting V2_1 it seems to implement a ServicePartitionClient2 which appears to be incompatible with RemotingClientVersion.V2_1

Below you can see where it blows up

and here you can see the properties on the proxy

if i set the listener name as per IActorService actorServiceProxy = ActorServiceProxy.Create(new Uri(serviceUris[i]), partitionKey,"V2_1Listener");

I get a serialisation exception so I assume that i do need an ActorServiceProxy which has a different version of the ServiceRemotingPartitionClient?

Additional details

• this Actor Inferface has the assemblybinding as

[assembly: FabricTransportActorRemotingProvider(RemotingListenerVersion = RemotingListenerVersion.V2_1,
 RemotingClientVersion = RemotingClientVersion.V2_1)]

• Local Service Fabric (not mesh) 5 node Dev cluster with 6.4 runtime installed
• Windows 2016 1607
• can replicate with both VS2017(15.9.3) and VS2019 Preview 1
• Microsoft.ServiceFabric (6.4.617)
• Microsoft.ServiceFabric.Actors (3.3.617)

[amanbha]

please use ServiceProxy.Create()

[tbertenshaw]

so the pattern in this repo for finding a generic actor is no longer supported?
service-fabric-dotnet-getting-started

[amanbha]

@tbertenshaw That pattern is supported as well, let me try to repro and look into whats going in the scenario you explained above.

[tbertenshaw]

hi @amanbha yeah the change below worked.... when the subsequent GetActorsAsync was called.

// IActorService actorServiceProxy = ActorServiceProxy.Create<IActorService>(new Uri(serviceUris[i]),partitionKey);

//to

IActorService serviceProxy = ServiceProxy.Create<IActorService>(new Uri(serviceUris[i]), new ServicePartitionKey(partitionKey));

[tbertenshaw]

@amanbha have you managed to replicate the issue or do you want a repro?

[amanbha]

@tbertenshaw I haven't tried it yet, it would be great if you could share the repro.

[tbertenshaw]

Hi @amanbha , if you clone the repo, and debug on a local 5 Node dev cluster then navigate to the endpoint home/GetAsync and you hopefully will reproduce the error on line 64 of the HomeController.

https://github.com/tbertenshaw/ActorRepro

[amanbha]

@tbertenshaw Thanks for sharing it, I will look at it, just want to make sure that you are not blocked and you can use ServiceProxy.Create to workaround this.

[tbertenshaw]

Yeah thanks serviceproxy worked for me On 7 Dec 2018 19:22, Aman Bhardwaj <notifications@github.com> wrote: @tbertenshaw<https://github.com/tbertenshaw> Thanks for sharing it, I will look at tit, just want to make sure that you are not blocked and you can use ServiceProxy.Create to workaround this. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#159 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AB6rkuNEEde_aAMfZmSP77KmpNl-WTN9ks5u2r_3gaJpZM4ZC6w9>.

[suchiagicha]

@tbertenshaw
This doesn't work for you as we check attribute at interface level and if not found then assembly level.
IActorService interface wont be having these attribuites and default we select V2 for Actors.
Correct way would be to add Assembly attribute at assembly level instead of interface level for your usecase.

[tbertenshaw]

Is this a bug? I generated the actor from file new project, it added the attribute to the interface. From: suchiagicha <notifications@github.com> Sent: 10 December 2018 19:41 To: Microsoft/service-fabric-services-and-actors-dotnet <service-fabric-services-and-actors-dotnet@noreply.github.com> Cc: timbo <tbertenshaw@hotmail.com>; Mention <mention@noreply.github.com> Subject: Re: [Microsoft/service-fabric-services-and-actors-dotnet] NamedEndpoint V2Listener not found in the address '{"Endpoints":{"V2_1Listener":".... (#159) @tbertenshaw<https://github.com/tbertenshaw> This doesn't work for you as we check attribute at interface level and if not found then assembly level. IActorService interface wont be having these attribuites and default we select V2 for Actors. Correct way would be to add Assembly attribute at assembly level instead of interface level for your usecase. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#159 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AB6rkk76DXH03NwsopUbgKCSO3n9SrS-ks5u3rjkgaJpZM4ZC6w9>.

[suchiagicha]

@tbertenshaw
Its not a bug. You are using IActorService interface but you don't have any attributes on it.
Hence for these kind of interface , you should do assembly level attributes instead of interface.

[tbertenshaw]

So its not a vs tooling bug then? Am I missing something or should there be documentation on this? It doesn’t seem intuitive.

[suchiagicha]

@tbertenshaw
Just to be clear , you should be adding attribute to your entry assembly like your client process .
No its not a bug. We don't generate template for IActorService. We will update the documentation with this info. Thanks for the feedback.