Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
MIT License
82
stars
12
forks
source link
Internal HTTP communication does not work on local cluster, possible .Net Core bug #278
The Votingapp works great when deployed to Azure. It does not work for me locally.
I get the same experience when creating 2 API services and try to talk to them over HTTP.
Have tried both the code from voting app as well as spun up 2 services and used RestSharp.
Basically, http://localhost:20002/api/pnl works in the browser (the backend service).
I can even use the servicename.appname instead of localhost in the browser, so clearly it works, it gives me a string back.
But the first service can't talk to this backend service from inside SF, which is very strange.
The Votingapp gives me this error:
System.Net.Http.WinHttpException: A connection with the server could not be established
Note I'm using localhost to get around the DNS issue. Fixed by changing the cluster setup script, changed a parameter to FALSE so it doesn't use the FQMN
The Votingapp works great when deployed to Azure. It does not work for me locally. I get the same experience when creating 2 API services and try to talk to them over HTTP. Have tried both the code from voting app as well as spun up 2 services and used RestSharp.
Basically, http://localhost:20002/api/pnl works in the browser (the backend service). I can even use the servicename.appname instead of localhost in the browser, so clearly it works, it gives me a string back.
But the first service can't talk to this backend service from inside SF, which is very strange.
I wonder if this core bug is involved?
https://github.com/dotnet/corefx/pull/28375
The Votingapp gives me this error: System.Net.Http.WinHttpException: A connection with the server could not be established
Note I'm using localhost to get around the DNS issue. Fixed by changing the cluster setup script, changed a parameter to FALSE so it doesn't use the FQMN