Connection refused (only) when using internal container-app name

[watts-agb]

• [ X ] documentation issue or request

Issue description

We have observed that when calling a container-app by the internal name, we are experiencing the following error during moderate load:

Message | Connection refused (name-of-container-app:80) Connection refused
Exception type | System.Net.Sockets.SocketException

According to the documentation here https://learn.microsoft.com/en-us/azure/container-apps/connect-apps?tabs=bash#call-a-container-app-by-name, this should be a valid approach.

The way we currently mitigate it, is to replace the internal name with the fqdn of the container app e.g name-of-container-app.happyhill-70162bb9.canadacentral.azurecontainerapps.io

After the mitigation, no errors with Message | Connection refused (name-of-container-app:80) Connection refused appears.

Additional context

Is this expected, but un-documented behaviour ?

Any insights into this would be greatly appreciated.

[anthonychu]

@watts-agb Can you please share your apps' resource IDs as well as the timeframe in which this occurred to acasupport@ microsoft.com so we can investigate? Please reference this GitHub issue. Thanks.

[watts-agb]

@anthonychu Mail has been sent with (additional) information. Please feel free to reach out if I can provide more info.

[simonjj]

We've confirmed this issue and are working on a possible fix. Please stay tuned for updates.