On 1/16/07, Brian Sullivan [EMAIL PROTECTED] wrote:
On 1/16/07, Dieter Maurer [EMAIL PROTECTED] wrote:
Try Florent's DeadlockDebugger to determine what you unuable
Zope is doing. It may tell you where Zope hangs.
Ok thanks -- I will have a look.
Ok so I have DeadlockDebugger installed
Ok so I have DeadlockDebugger installed and running ( I think) -- it
produces an on screen dump that looks the following (this is under
normal circustances -- without the failure that I was trying to
debug happening). I am just trying to get a feel for what I am seeing.
I see this same
On 1/17/07, Maciej Wisniowski [EMAIL PROTECTED] wrote:
Ok so I have DeadlockDebugger installed and running ( I think) -- it
produces an on screen dump that looks the following (this is under
normal circustances -- without the failure that I was trying to
debug happening). I am just trying
: Re: [Zope] pool_size
On 1/17/07, Maciej Wisniowski [EMAIL PROTECTED]
wrote:
Ok so I have DeadlockDebugger installed and running ( I think) --
it produces an on screen dump that looks the following (this is
under normal circustances -- without the failure that I was trying
to debug
On 1/17/07, Doyon, Jean-Francois [EMAIL PROTECTED] wrote:
This information is also available in the Control Panel's debug section.
You can see which thread is busy doing what ...
Depending on exactly how locked up it is, you can try going there, see
what the current requests are pending, and in
Used to use the debug a lot but then when we found DeadLockDebugger
(DLD), I was hooked...mainly because there is no 'baggage' to loading
the page. Debug actually uses one of the threads to show you that page.
The content of the thread sorta looks like the whole REQUEST object,
which is
Brian Sullivan wrote at 2007-1-15 11:27 -0500:
I am having a problem with zope 2.9.4 occasionally pegging the CPU and
thereafter being unusable -- there are some indications in the event
log that this is related to pool_size being too small.
Under under very special cases should a too small
On 1/16/07, Dieter Maurer [EMAIL PROTECTED] wrote:
Try Florent's DeadlockDebugger to determine what you unuable
Zope is doing. It may tell you where Zope hangs.
Ok thanks -- I will have a look.
___
Zope maillist - Zope@zope.org
I am having a problem with zope 2.9.4 occasionally pegging the CPU and
thereafter being unusable -- there are some indications in the event
log that this is related to pool_size being too small.
Lacking any other strategy to determine the cause of the problem, I am
considering experimenting
