Thanks a lot, that's informative. Dead time: 30 I have only 1 active request over the 13 instances. Yes 20 min is really too much: We have some request which can take up to 1-2 min. In the apache log, I saw http error 500.
I found the source of the "No error" displayed in the browser: It comes from the adaptor when the response is null and error has not been set (see transaction.c) Dominique On Oct 15, 2013, at 10:54 AM, Alexander Spohr <[email protected]> wrote: > Did you check /WebObjects/WOAdaptorInfo? > What is the dead time? > Do you see a lot of active requests? > > > Am 14.10.2013 um 15:26 schrieb Schoenenberger Dominique > <[email protected]>: > >> Thanks, >> >> My parameters are (bigger): >> >> HTTP Adaptor Settings: >> Load Balancing scheme: Round Robin >> Send Timeout: 1200 >> Receive Timeout: 1200 > > Do you have requests that take longer than 20 minutes? > > >> The page seems related to an http error 500. > > Is it a 500 or another 5xx? > > >> Is any way to avoid the adaptor to give the request to another instance if >> one instance is too slow to respond because this seems no helping because at >> the end it causes a "Session timeout" error. > > This would just hide your problem. You need to fix it. > > >> I need also to say that when the user get a untimely "Session Timeout", >> there is not waiting time (We got the session timeout just after the click >> on a button). I would expect some retrying before returning an Session >> timeout error if it is due to a instance not responding. > > The apache has already decided that your instance is dead because it did not > answer in time. So it just kicks your request to the next instance. > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
