Connection Errors with 2003 Server

[ConvertFromOldNGs]

by Stephen >> Thu, 18 Nov 2004 4:06:12 GMT

I have just upgraded our Test server to Windows 2003 server, and now get Connection errors with our web application. If no requests are made it will work fine and stay running indefinately..... but as soon as requests are made, even if its only 1 request, handled by only 1 of the 3 web application monitors, it appears as though after a period of inactivity all the web monitors show a "Connection Error 31008: connection read error", even the ones that had no requests made to them. The logs show absolutely nothing. They don't even log the connection error. Any requests then made to the application are unsuccessful, get the server unavailable message.
Any ideas?!?!

Thanks
Stephen

[ConvertFromOldNGs]

by BeeJay >> Thu, 18 Nov 2004 6:15:48 GMT

To help increase security for your Web server, IIS is configured, by default, to serve only static content after you install it on Windows Server 2003. You must manually enable programmatic functionality by enabling the appropriate Web service extension in the Internet Information Services (IIS) Manager snap-in. (Refer to the IIS 6.0 / Windows Server 2003 documentation for further details.)

I'm not sure whether you were already aware of this or not, but if you have already done this then please ignore my posting and I'll step aside and let someone else help out.

Cheers,
BeeJay.

[ConvertFromOldNGs]

by Stephen >> Thu, 18 Nov 2004 19:12:44 GMT

Thanks, I had noticed that. So I have left all dynamic content disabled, and I have set up a Jade extention that allows only jadehttp.dll.
So it is processing the requests OK, it's just that after a period of inactivity (typically about 20 minutes, but does vary) the connection error just appears for apparently no reason. No request is being made at the same time, it just happens of its own accord.

[ConvertFromOldNGs]

by allistar >> Thu, 18 Nov 2004 19:35:18 GMT

What version of JADE are you using? I ask because W2003 is only supported after (IIRC) JADE 6. That may not be the reason for this issue but if you are on an older version of JADE does upgrading remove this problem?

Allistar.
--
------------------------------------------------------------------
Allistar Melville
Software Developer, Analyst allistar@silvermoon.co.nz
Auckland, NEW ZEALAND

Silvermoon Software
Specialising in JADE development and consulting
Visit us at: http://www.silvermoon.co.nz
*NEW* Simple web access to Jade at: www.silvermoon.co.nz/jhp.html ------------------------------------------------------------------

[ConvertFromOldNGs]

by Stephen >> Thu, 18 Nov 2004 19:49:30 GMT

It was on 6.0.19, and I have just tried putting the latest 6.0.20 on it and it still does it.

[ConvertFromOldNGs]

by jcampbell >> Thu, 18 Nov 2004 23:58:38 GMT

Have you set this up in a seperate application pool or is it using the default pool ? What are the properties on the pool it is using re recycling etc ?

[ConvertFromOldNGs]

by Stephen >> Fri, 19 Nov 2004 0:46:08 GMT

Ah ha!!
Thank you very much! It was using the default application pool, which had the option "Shutdown worker processes after being idle for 20 minutes".
Just as a matter of curiosity, as I assume you are running Jade web services under 2003 server, and recommendations for what sort of settings to use?

[ConvertFromOldNGs]

by jcampbell >> Fri, 19 Nov 2004 0:59:57 GMT

We actually run each website in seperate application pool so we can configure the 'anonymous user as it were' because we run multiple websites for different Jade systems off the one IIS. Also allows for replacement of jadehttp.dll etc without impacting on other web sites.
Apart from that we just set the application pool to not shutdown unless manually unloaded - everything else pretty much default.

Think that's about it.