Action to action call fails for "9001:9000" proxy port


I have one service and everything works if the proxy’s external port is 9000. However, if I change it to 9001, any action to action calls fail, even though they are within the same service.

version: "3"
    command: -Dconfig.resource=dev-mode.conf -Dlogback.configurationFile=logback-dev-mode.xml
      - "9001:9000"
      - "host.docker.internal:host-gateway"
      USER_FUNCTION_HOST: ${USER_FUNCTION_HOST:-host.docker.internal}
      PUBSUB_EMULATOR_HOST: gcloud-pubsub-emulator

I think the action to action call fails because it assumes the other action is on port 9000.

Connection refused: localhost/

I’m not sure what setting I’m missing, and I can’t see it in the documentation.


Given the “we are currently working on making running multiple services locally for development easier.” comment from @aludwiko in Unable to listen the event for service to service eventing config, I’m guessing this isn’t working currently?

It works, although requires additional changes:

    command: -Dkalix.proxy.http-port=9001 -Dconfig.resource=dev-mode.conf -Dlogback.configurationFile=logback-dev-mode.xml 
      - "9001:9001"

and you need to run user function with:


As mentioned before, we are working to simplify this setup.

Everything is ready to go in *-eventsourced-customer-registry-subscriber samples. I would encourage to start with them. You can run them without the publishing side *-eventsourced-customer-registry just ignore warnings about:

[info] 11:11:35.911 WARN  kalix.javasdk.impl.DiscoveryImpl - Warning reported from Kalix system: KLX-00426 Direct eventing in service [host.docker.internal:9000] is failing, will be retried
[info] Could not connect to [host.docker.internal:9000]

Everything is ready to go in *-eventsourced-customer-registry-subscriber samples. I would encourage to start with them.

I should study the examples as much as the documentation :smiley: Thanks, it works now.