Description:
------------
A php script that didn't check the odbc_connect return value entered a state
where it did not end.  The httpd server does not seem to time these requests out
and reports the as "W" Sending Reply state.  Eventually this causes access
denial due to max_connection limit being reached.  I upgraded to httpd 2.2.0 and
php 5.1.1 but the problem still occurs.

This is the timeout value from httpd.conf
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

This is the timeout value from php.ini
max_execution_time = 120     ; Maximum execution time of each script, in seconds
max_input_time = 60     ; Maximum amount of time each script may spend parsing
request data
memory_limit = 8M      ; Maximum amount of memory a script may consume (8MB)


server-status entry:
0-0	27217	2/2/2	W 	0.00	3284	0	13.2	0.01	0.01 	ceason	madmax	GET
/status/ras_results.php?db=bgs1&severityCB=1&facilityCB=1&b


I initially reported this as an Apache bug and received this response.

This is a bug in mod_php.  If mod_php does not return the control of execution
from the script, httpd can't do anytning.  Please report this to the PHP
Project, instead of Apache HTTP Server Project.



Reproduce code:
---------------
$dbconn =  odbc_connect("BOGUS","username","password");
$query = "select * from footable";
 while(odbc_fetch_row($result)) {
 print"$result";  
 } 


This may fail correct the 1st time.  Hit refresh after this and it should hang up.

Expected result:
----------------
Similiar error messages as below


Warning: odbc_connect() [function.odbc-connect]: SQL error: \EA, SQL state D\$ in SQLConnect in /var/www/html/test.php on line 14

Warning: odbc_fetch_row(): supplied argument is not a valid ODBC result resource in /var/www/html/test.php on line 16

Actual result:
--------------
Hang after refresh