nospanov
asked on
502 Bad Gateway error on client when i host my WCF service to the IIS 7.
Hello
When i call wcf service locally, it works fine.
when i call my wcf service hositing it on IIS i get error 502. It happens exactly after 90 secs. So i thing it is some timeout issue...
I tried to change following setting on IIS on mywebsite and default website settings.
In website - connectiontimeout - set to 600 instead of 120
in application pool Ping maximum respond time - 600 instead of 90, ShoutDownTimeLimit = 600 instead of 90 and start uptime limit, instead of 90
I consume WCF through win 8 app client, setting are following:
client.Endpoint.Binding.Re ceiveTimeo ut = new TimeSpan(0, 3, 0);
client.Endpoint.Binding.Cl oseTimeout = new TimeSpan(0, 3, 0);
client.Endpoint.Binding.Op enTimeout = new TimeSpan(0, 3, 0);
client.Endpoint.Binding.Se ndTimeout = new TimeSpan(1, 0, 0);
As i said, it works locally
WCF works through http
What else it can be?
When i call wcf service locally, it works fine.
when i call my wcf service hositing it on IIS i get error 502. It happens exactly after 90 secs. So i thing it is some timeout issue...
I tried to change following setting on IIS on mywebsite and default website settings.
In website - connectiontimeout - set to 600 instead of 120
in application pool Ping maximum respond time - 600 instead of 90, ShoutDownTimeLimit = 600 instead of 90 and start uptime limit, instead of 90
I consume WCF through win 8 app client, setting are following:
client.Endpoint.Binding.Re
client.Endpoint.Binding.Cl
client.Endpoint.Binding.Op
client.Endpoint.Binding.Se
As i said, it works locally
WCF works through http
What else it can be?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.