CPU's are averaging about 50% load & are not maxing out, so there's plenty of
headroom there.
The logs show no signs of any errors.
Hmmm. Haven't tried mod_status. I'll take a look and see what it tells me.
NT wouldn't be my first choice either but *nix isn't a corp. standard. Yet
;-)
Thanks for the advice,
Simon Wilcox.
Intranet Development Manager
Williams Lea Group
>From "David Rees" <[EMAIL PROTECTED]> Date 16:28:08 9 August
2000
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Simon Wilcox/BASE/WilliamsLea)
Fax to:
Subject: RE: Connect failures
> However, under https, when it saturates at about the same level, the
> server starts refusing connections.
>
> Is this the correct behaviour and is there any way to stop
> these errors ?
I'm not familiar with running Apache under NT, but hopefully the same
debugging techniques can be used as under unix. Here's the things I would
check:
CPU Usage: using the task manager, is it maxing out?
logs: Do the logs indicate any problems?
mod_status: Have you set up mod_status and seen what is going on?
Apache 1.3.X is known to not perform optimally under NT, Apache 2.X when it
is released should do much better.
-Dave
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
