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

Actor method invocation should work

Actual Behavior

"errorCode": "ERR_ACTOR_INVOKE_METHOD",
"message": "error invoke actor method: error from actor service: System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it. (127.0.0.1: 3500) \r\n ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.\r\n at System.Net.Sockets.Socket.

Steps to Reproduce the Problem

run a .NET 6.0 service with actors

debug in VS Code with task:

"label": "debug", "type": "daprd", "appId": "yatp-tick", "appPort": ..., "httpPort": <not 3500>, "dependsOn": "build"

invoke an actor method with curl or postman on

http://localhost : <not 3500> /v1.0/actors/Type/Name/method/Method

N.B.1 - launching the application with dapr cli works
N.B.2 - using the default port 3500 (-> removing "httpPort": <not 3500>) also works

@francotiveron What platform are you using (e.g. Mac, Linux, or Windows), and which version of the Dapr extension for VS Code? I don't see this issue with the latest build on my Mac. It may be that the extension is unable to extract the HTTP port when polling for Dapr instances for whatever reason, in which case, it falls back to port 3500 .

@philliphoff Did you try to call an actor method from postman at

http://localhost:3507/v1.0/actors/Type/Name/method/Method ?

Below my situation:

There is something wrong on the VS code extension when working with actors.
I find several issues when changing the port from the standard 3500. For example, accessing the actor state manager in OnActivateAsync fails with ERR_ACTOR_INSTANCE_MISSING.

Unfortunately, as with multi-targeting different ports are required, this makes impossible to debug multiple micro-services together in VS Code