DO NOT REPLY [Bug 9485] New: - Sockets not being read when under load on MS ISA Firewall

[bu...@apache.org]

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=9485>.
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=9485

Sockets not being read when under load on MS ISA Firewall

           Summary: Sockets not being read when under load on MS ISA
                    Firewall
           Product: Apache httpd-2.0
           Version: 2.0.36
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mpm_winnt
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: craig@freeasphost.co.uk


(As I posted to comp.infosystems.www.servers.ms-windows &  microsoft.public.isaserver 
without any luck)


I've been running Apache 1.3.2x on my ISA firewall, to "hide" 
several
internal IIS webservers for about a year, very successfully. I
accomplished this by 
placing Apache on my firewall, and setting an
incoming protocol filter on port 80 in ISA 
Management, and then
used mod_proxy to forward different virtual host requests to 
various
internal IIS boxes.

However, since Apache2's release I have been wanting to 
upgrade site
(20-30k requests/day) to the new release. However all test runs of
Apache 2 (on a 
different port) have shown it's performance to be
miserable (despite all the official 
benchmarks around the internet).

I have been trying to find out why, and have discovered that 
Apache2
is not closing it's sockets when a request is finished for some
reason. This problem 
did not happen on Apache1.

I verified this problem by telnetting to port 9001 and performing 
an
HTTP get. If I do this to the internal Apache IP address, I get
disconnected at the end of the 
request, however if I do this from
"outside", the connection is not disconnected at the end of 
the
request.
It opens the sockets, and doesn't respond to the request,
and stays in 
"Reading" mode, and once there are no threads left
Apache2 stops responding. [It can stop 
responding before all threads
are used by not opening the sockets.]

I have saved an example 
mod_status page during the load 
test:
http://www.freeasphost.co.uk/support/freeasphost.co.uk9001.html
Sockets 
marked Reading stay open after the loadtesting is finished.

Has anybody experienced this 
problem, or know of any reason why this
should happen. I have tried forcing Apache to bind to a 
certain IP
address, instead of "0.0.0.0". (ie not bound to a particular IP address)
I have 
read that Apache 2 is now using a similar socket model to IIS.

Could it be that it is socket 
pooling, and therefore gaining the same
affliction as IIS has with ISA, described 
here:
http://www.isaserver.org/shinder/tutorials/socket_pooling.htm

Apache 
2.0.36, downloaded MSI binaries

My firewall is set up in exactly the same way as I use for 
Apache1 on
port 80.

Many thanks, and I would be greatly obliged if anyone could solve 
this
problem

Craig Macdonald
craig{at}freeasphost.co.uk
freeASPhost.co.uk 
Administrator

---------------------------------------------
Load test results:
(These are all hitting the same backend IIS box, just 
using
different versions of Apache and mod_proxy)

Running test 1 (apache 
1.3.22/mod_perl-1.22)
12 fetches, 38 max parallel, 178896 bytes, in 10.0078 seconds
14908 
mean bytes/connection
1.19907 fetches/sec, 17875.7 bytes/sec
msecs/connect: 485.759 
mean, 810.484 max, 99.456 min
msecs/first-response: 739.271 mean, 1580.97 max, 237.383 
min
HTTP response codes:
  code 200 -- 12

Running test 2 (apache 2.0.36)
1 fetches, 49 max 
parallel, 14908 bytes, in 10.0048 seconds
14908 mean bytes/connection
0.0999519 
fetches/sec, 1490.08 bytes/sec
msecs/connect: 126.339 mean, 126.339 max, 126.339 
min
msecs/first-response: 189.68 mean, 189.68 max, 189.68 min
HTTP response codes:
  code 
200 -- 1

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org