|
Posted by Joshua Ruppert on 08/08/06 22:23
Chung Leong wrote:
> Joshua Ruppert wrote:
> > Chung Leong wrote:
> > > Joshua Ruppert wrote:
> > > > Ok, It took a little while but I currently have one orphaned process
> > > > and it has just one thread and it seems to still be in the
> > > > initialization phase of the base PHP environment. The thread is labeled
> > > > as php.exe!OS_SetFlags+0xa0. The stack for the thread looks like this:
> > > > ntkrnlpa.exe+0x8cf3e
> > > > ntkrnlpa.exe+0x2927a
> > > > ntkrnlpa.exe+0x32cee
> > > > ntkrnlpa.exe+0x32f95
> > > > ntkrnlpa.exe+0x2927a
> > > > ntkrnlpa.exe+0x137e4c
> > > > ntkrnlpa.exe+0x88c6c
> > > > ntdll.dll!KiFastSystemCallRet
> > > > kernel32.dll!WaitForSingleObject+0x12
> > > > php4ts.dll!zend_timeout+0xac
> > > > php.exe+0x1e90
> > > > php.exe!OS_SetFlags+0x183
> > > > kernel32.dll!IsProcessorFeaturePresent+0x9e
> > > >
> > > > Any thoughts?
> > >
> > > Hmmm... The script is definitely timing out. PHP is just having trouble
> > > exiting out cleanly. zend_timeout() does one of two things: it either
> > > calls exit() to terminate the process immediately, or it does a
> > > longjmp() to a bailout point set earlier. Usually it's the latter.
> > > Whatever it's doing it's fubar...
> > >
> > > One thing to try is set time limit to 0 (i.e. infinite). At least then
> > > PHP wouldn't fall into this trap.
> >
> > Are you refering to the max execution time?
>
> Yes.
Ok thanks. I'll see if that changes anything. We're also switching over
to a setup with twice the horsepower, to mitigate the possibility of a
resource limitation creating the problem. Thanks again for all your
help.
Navigation:
[Reply to this message]
|