Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to get V2 remoting working #309

Open
Gerrilicious opened this issue Mar 1, 2022 · 1 comment
Open

Unable to get V2 remoting working #309

Gerrilicious opened this issue Mar 1, 2022 · 1 comment

Comments

@Gerrilicious
Copy link

Describe the bug
When trying to call stateless service with V2_1 Listener from WebApi (http endpoint) to the service it works, with the exclusive V2 I get the error: "NamedEndpoint V2Listener not found in the address ..."

To Reproduce
Minimal reproduceable example: https://github.com/Gerrilicious/FabricApplicationCommunicationTest

Steps I have done:

  • Create new Service Fabric Project in Visual Studio (FabricApplicationCommunicationTest)
  • Add ASP.NET Core Web Api Stateless Service to Fabric application (Web)
  • Add new Service Fabric Application (Fabric Application containing Services)
  • Add Stateless .NET Core service & setup for V2 remoting: Add assembly attribute to stateless service (V2 exclusive) & Change endpoint listener of stateless service to: "ServiceEndpointV2"
  • Add Class Library containing Service interface for communication (IStateless1)
  • Add API in Web API an build service proxy call to Stateless1
  • Call API from Browser for example

Expected behavior
I expect clarification on how the V2 stack should be used.

  • What requirements does the caller who wants to call V2 remoting interface need to have?
  • Working example would be greatly appreciated

Additional context
Add any other context about the problem here.

@pakunapamsft
Copy link
Contributor

ServiceFramework checks for the *ServiceRemotingProviderAttribute in the interface assembly and Entry assembly in order.
You need to either move FabricTransportServiceRemotingProviderAttribute to Communication project(interfaces) or have it defined in Web project as well inorder to be able to read by ServiceFramework.

#3 in remoting doc(https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-communication-remoting#use-an-assembly-attribute-to-use-the-v2-stack) suggests adding the attribute in the interfaces library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants