ID: 18271
Updated by: Brendan@callaghans.com.au
Reported By: Brendan@callaghans.com.au
Status: Open
Bug Type: IIS related
Operating System: Win2000 Server
PHP Version: 4.2.1
New Comment:
Have confirmed that the error occurs using Mozilla 0.9.4 and Netscape
Communicator 4.78 under Mandrake Linux.
These are older browsers, but it is clear that the error isn't IE6
specific.
Previous Comments:
------------------------------------------------------------------------
[2002-07-11 05:06:45] Brendan@callaghans.com.au
Upgraded to 4.2.1, no change.
Did some more searching of the bugs database, found 15324 and 14937
seemed to be similar problems to mine, but didn't find any solutions.
It's becoming evident that the request is being passed to php.exe, but
that PHP immediately fails to process the script, and instead of
responding with an error, it just hangs. IIS reacts to this
non-response by dropping out a 502 error code and a "CGI Timeout"
message.
Might try ADP next.
------------------------------------------------------------------------
[2002-07-11 03:24:30] Brendan@callaghans.com.au
I have been examining various log files, and have identified the
following:
When this event occurs, the Windows Event Viewer records an error from
the W3CSVC service, stating that the request was not fulfilled within
the allowed timeout, and so the request was deleted.
The IIS error logs record the request as having failed with a 502 HTTP
code. A 502 is defined as "Bad Gateway", so not very helpful.
I tried switching on the config directive "display_startup_errors", but
this had no effect.
The data being sent in the POST are one small integer (three digits
max) and one four-character string. And the hang is only triggered for
very particular combinations of the two variables. What has got me
tearing my hair out is that the script is failing before it has a
chance to even try operating on the data. So how could the contents of
the data be making a reproducible difference? How could "169" and
"2002" work perfectly, but "170" and "2002" cause the script to hang?
It just doesn't follow.
------------------------------------------------------------------------
[2002-07-10 22:57:23] Brendan@callaghans.com.au
Haven't been able to try that - the site is intranet only, with a
standardised operating environment on the workstations. There's no
other browser installed and I'd have to get permission from the SA to
install one.
But I'll have a chat to him and see if I can arrange a test.
------------------------------------------------------------------------
[2002-07-10 22:51:01] sniper@php.net
Does this happen with other browsers? Like NS or Mozilla?
------------------------------------------------------------------------
[2002-07-10 22:41:51] Brendan@callaghans.com.au
Platform information:
Windows 2000 Server
IIS 5
MSSQL 2000
Hi,
For some time now, my PHP site has been experiencing an intermittent
problem - very elusive.
Every now and then, a user would try to do something and the next page
simply would not load. All my users are accessing the site with IE6,
and when the hang occurs, the status bar displays the text "Opening
page ****...", and the blue status indicator crawls slowly to the
right. But nothing happens. The screen doesn't even clear from the
previous page. No errors, no warnings. I even tried turning on
E_NOTICE, but none of those either. This continues for a couple of
minutes, until IIS gives up and reports a CGI Timeout.
Typically, if the user closed all his IE windows, and then went back
in, things would work normally again. So I assumed it had something to
do with accumulating too much session data (hence, destroying the
session by closing all the IE processes cleared things up). And since
it was not reproducible, I couldn't do very much about it. However,
just recently we discovered a series of actions which reproduces the
problem, regardless of how "fresh" the session is.
The page in question is quite simple compared to some of the other
pages in the site, which is why I find it curious that it should
trigger the bug consistently. When you first load the page, it
presents a HTML form, asking the user for some data. When the form is
submitted (it submits back to the same php file), the page generates a
fairly basic report.
The bizarre part is that with certain data inputs, the report runs fine
(and total execution time is about a third of a second), and with
certain other data inputs, the report will not load at all. This page
doesn't put any data in the session, the code doesn't use any
particularly exciting functions, and I can't discern any relevant
difference between the data input which works, and the data input which
triggers the hang. I can't debug it using PHP code, because it doesn't
even reach the stage of outputting HTML.
I am very confused and looking for a hint as to how I can proceed. I
searched the bug database, but didn't find any matches to my problem.
The bug is causing some serious angst in my user base. Any assistance
will be greatly appreciated.
BJ
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=18271&edit=1