You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/08/06 23:46:09 UTC
DO NOT REPLY [Bug 18037] -
100% CPU Usage with Apache 2.0.44
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18037>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18037
100% CPU Usage with Apache 2.0.44
emmanuel_ae@yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
Resolution|INVALID |
------- Additional Comments From emmanuel_ae@yahoo.com 2003-08-06 21:46 -------
On Win XP Pro its Mcafee Virusscan 7 (both home and pro editions) that cause
the problem with or without the firewall installed. After uninstalling mcafee
viruscan 7 and rebooting the problem disappears.
However the problem excessive cpu usage does not occur with apache 1.3. I
shifted to that and it seems to work fine. That may be a solution.
I did try to probe a bit into the differences between apache 1.3 and 2.0.
2.0 has been written from scratch for windows.
Superficially the differences that i could see was that 1.3 does not have a
tray monitor and has a much bigger conf file.
However exiting the apache monitor also does not help.
It must be something about apache 2.0's bind code i guess. And i dont think
asking mcafee to change their product will prove useful. It maybe easier to
figure out whats causing the problem in apache 2.0 and fix it.
Till then use apache 1.3
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org