Posted by Joshua Ruppert on 08/03/06 13:57
Chung Leong wrote:
> Joshua Ruppert wrote:
> > Conversely when a PHP process is stuck for longer than the max
> > execution time, I've never seen them be recycled. Though one of our
> > problems is that we don't know when the PHP processes were started
> > versus the start of the DB connect. So we don't know how long they have
> > been sitting, but we have highlighted some of them and waited 15 - 20
> > min without them going away. Do you know if the process start time
> > stored anywhere under the hood in Windows?
>
> Install ProcessExplorer by Mark Russinovich. It'll get you the info you
> need. Here's the link:
>
> http://www.sysinternals.com/Utilities/ProcessExplorer.html
>
> Right click on the process and select properties. The start time is
> near the bottom.
Ok now I'm really confused. Yesturday I found some more stranded
processes (we usually get at least a few every few days). When I loaded
up the Process Explorer the properly running PHP processes were all
listed under w3wp.exe, which I'm assuming is the IIS worker process.
The processes that were stalled were all at the base level where you
would see the System Idle Process and Explorer. I'm not sure what this
means.
Could it mean that they are being triggered by something outside of
IIS?
Are the processes not imediately associated to IIS? (If that is true
then it seems that the processes are failing very early in their
execution.)
Navigation:
[Reply to this message]
|