Posted by Jim Michaels on 11/26/07 03:25

C. (http://symcbean.blogspot.com/) wrote:
> On 25 Nov, 11:33, Ulf Kadner <dr_lo...@gmx.net> wrote:
>> Jim Michaels wrote:
>>> now the browser sits there forever waiting for the server to respond. I
>>> even tried bouncing the server. no joy.
>> You never have to run untested Code into productive Environments.
>> If its not productive install and use a debugger for locating the problem.
>>
>> Otherwise u can only use manual debugging (print_r, var_dump, ...)
>> to clean the problems.
>>
>>> the file is 700 lines long, so I decided not to post it here.
>> So you can only quest a magic glass ball or consult your rather clairvoyant.
>>
>
> try publishing a 10 line script which replicates the problem (although
> by then you'll probably have worked it out for yourself).
>
> C.

in php.ini:
max_execution_time = 60 ; Maximum execution time of each script, in
seconds

it waits a whole lot longer than that. it won't ever stop. usually I
see a browser timeout after a certain number of seconds, but this has me
stumped. it would be nice to know what's going on under the hood.

is this apache which is having a problem? this is not on a production
server, just a test environment.

--
Jim Michaels
for email, edit the address

[Back to original message]