IIS5.0 Timeout problem
From: Michael Dimento (michael.dimento_at_om.com)
Date: 08/05/04
- Next message: Sanjay Singh: "Re: IIS getting down frequently"
- Previous message: WenJun Zhang[msft]: "Re: IIS Setting prevents AD Query from working?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 4 Aug 2004 21:09:28 -0700
I've got an application written usind VS2002, using WSE
1.0 (Web Extensions) and against IIS5.0. And Windows 2000
I have a Windows form that calls a web service that in
turn queries a databse and returns the data in a dataset
back to the form.
The form requires a login, in which those details are used
as the credentials for the web server.
I'm using Windows Authentication in the web.config file. I
have all the possible timeouts that I can find to set, set
at 60 mins. The "sessionState" timeout is set to 60 mins.
I have the default web site "Connection Timeout" set to 60
mins. Under the virtual directory for the web service app,
under configuration and then on the tab "App Options", I
have Session Timeout set to 60 mins.
This works fine, until after about a period of 15-20
minutes the web service returns a "request time out
error". And this error sometimes will come back as xml as
is expected by the web service, but most of the time
as "Client found response content type of text/html, but
expected text/xml". The error message in the html is the
500 Request Time Out.
Why dopesn't this come back as an xml respons eto the web
service like all other IIS errors?
Why is this timing out all the time after a short period
of time ? And even if it does timeout, the forms app has
the web proxy credentials set correctly, and so why
doesn't it connect again ?
If i accept the error and try again, sometime sit works,
and sometimes it gives me same error. And if I modify the
web.config by just adding a " " or something, then it
works all the time. I guess this causes a JIT compile. But
I can't see why this would fix the timeout.
Does anyone know if this is a current IIS5.0 bug ? Or how
I can prevent these, or handle these timeouts ?
Would I have to recreate the web proxy in my c# forms code
each time, in order for it to make a new connection and
not try the connected session ?
I have even tried setting the "Keep-Alive" option for the
web server to false in order to make a new connection each
time, but this still gave me same results.
Any help in this area is greatly appreciated, as it's
driving me bonkers ;-)
Thanks
Michael Dimento
- Next message: Sanjay Singh: "Re: IIS getting down frequently"
- Previous message: WenJun Zhang[msft]: "Re: IIS Setting prevents AD Query from working?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
