Both TimeOut and KeepAliveTimeOut are set at 1 hour, which is way excessive for production environments, but it works well if you want the browser to wait while an application may be under control of a debugger.
I admit, that my configuration is constraining the HTTP server, excessively. Some runtime environments don't allow persistent connections.
-Nathan.
----- Original Message ----
From: Jim Franz <franz400@xxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Tue, June 15, 2010 5:12:09 PM
Subject: Re: [WEB400] Why did my HTTP server lock up?
what release?
do you keep up with the http group ptfs?
in over 12 yrs of http (classic & apache) i've only had 1 lock up when
running a comm trace and taking heavy traffic on a tiny machine (early
v5r3).
And i run maxcgi at 4 times what i expect..
What is your TimeOut value ?
The KeepAliveTimeOut seems way excessive.
Jim Franz
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
