We have ASP.NET Web Service running on IIS6 that has long-running methods (processing takes about 5 minutes).
When we call the web service from Win 2003 Server, our client gets HTTP 503 error after waiting for the response for couple of minutes. So we never get the response data back to the client, even though, the call is actually completed on the server (our application logging shows that the whole method gets executed). So the execution on the server side is not stopped, client just stops waiting for the response.
However, when we call the same method with the same parameters and the same client from Win XP workstation, everything works as expected and we don't get any HTTP errors.
Does anyone got any ideas why this error happens only when calling from Server OS?
Is there some registry or other setting where you can control how long OS waits for HTTP responses?
Related
Some time client not received message from Server when I call http request. When I deploy on IIS physic server, it working fine but when I deploy on App Service Azure sometime client not received message from Server . When I call from Chorme, client not received but I call for FireFox client received message normal.
In IIS, I have set the "Maximum worker processes" to 16 in application pool setting. Now, I have a request which will load for some time. At the same time, if another request is submitted, this request will not respond until the previous request finished loading. I am curious that I already set the worker process to 16. Is that supposed that IIS will handle the request concurrently with the available worker process? But as I observed, the latter request have response only after the previous request finished. Is that the requests are queued in only one worker process so that make it waiting? How can I make IIS handle the request concurrently without the waiting?
These are both timeout errors, but who is timing out in a 408 vs. a 504?
From w3, 408 is defined as:
The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
...And 504 is:
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
So who is the 'client' in the 408 if not an intermediary server? If it's an actual end user, how does a server know to wait for their request before they have made it?
The client is the browser or client application. The server knows to wait for a request because it has accepted a connection, or already read part of the request, say a header or two.
Amazon documentation tells: http://docs.aws.amazon.com/en_en/elasticloadbalancing/latest/classic/ts-elb-error-message.html#ts-elb-errorcodes-http408
Indicates that the client cancelled the request or failed to send a full request
Mozilla documentation tells: https://developer.mozilla.org/en/docs/Web/HTTP/Status/408
The HTTP 408 Request Timeout response status code means that the server would like to shut down this unused connection. It is sent on an idle connection by some servers, even without any previous request by the client
I'm struggling to find the timeout configuration in GlassFish 4 to solve the below problem:
The application implements a so-called tunneling, serving contents of few connecting portals to users. It opens up an HTTP connection, passes on user's request to one of the portal, receives response from the portal, and then passes the response on to the browser.
However, the problem occurs when one of the connnecting portals takes very long to response. When this happens, the application seems to give up waiting for the response and sends another request, exactly after 5 minutes, to the portal in question. This time it's a request for error/HTTP_BAD_GATEWAY.html.var
Does someone know how to increase this timeout?
I have a site using asp.net and WebAPI deployed on IIS 7.5. Normal site usage is steady but occasionally there are bursty spikes with very high usage and users get very slow response timeouts. There is no option to improve performance at this time and the client has asked for a quick fix involving a customised 503 error page with the same look as the rest of the site.
The single IIS server sits behind a load balancer and there is the option of adding a 2nd server purely to serve a static error page when the site is under heavy load. There has been a suggestion of a solution where slow responses trigger all subsequent requests go to the static server and get the custom 503 error page until the usage subsides.
As far as I can see its not possible to customise the default 503 error page that is served automatically by IIS when its request queue is full.
I can't see anything on SO about how to solve this sort of issue - can anyone help?
Load balancers use probes to check if a node is operational. One possible solution is to make your own probe that checks if load on a node has reached defined threshold. If so then the probe (your probe) would return HTTP 500 to load balancer. If load balancer receives this error code from probe then it will not forward requests to this node. When threshold is not reached then the probe would return HTTP 200.