Hello all,
I recently made a lot of changes to my ZODB app, and now I'm experiencing
some puzzling behavior.
Normally I have ~15 clients making requests to the server every few
seconds. Some of these
requests commit new data to the database, while others just process
existing data. I also
have a
On Thu, Apr 19, 2012 at 17:20, Claudiu Saftoiu wrote:
> My question is: what could possibly be causing the server to 'lock up', even
> on a
> simple view like 'is_alive', without using any memory or CPU? Is there some
> ZODB
> resource that might be getting gradually exhausted because I'm not hand
On Thu, Apr 19, 2012 at 11:33 AM, Martijn Pieters wrote:
> On Thu, Apr 19, 2012 at 17:20, Claudiu Saftoiu wrote:
> > My question is: what could possibly be causing the server to 'lock up',
> even
> > on a
> > simple view like 'is_alive', without using any memory or CPU? Is there
> some
> > ZODB
On Thu, Apr 19, 2012 at 18:22, Claudiu Saftoiu wrote:
> Are there locks that could possibly be used for the 'is_alive' function?
> Here is the
> definition in its entirety.
>
> In 'configure.zcml':
> view=".views.is_alive"
> name="is_alive"
> renderer="json"
> />
> in 'views.py'
>
> I have no idea; all you told is that you use the ZODB, not what server
> framework you use to register your views. Is this Grok, Bluebream,
> Repoze.BFG, Zope 2 or something else?
>
Ah yes, sorry about that. I'm using Repoze.BFG . Does that help any?
I don't think that is_alive would be the c
>
> I don't know, anything could lock up your site if something is waiting
> for a lock, for example.
>
> Use http://pypi.python.org/pypi/z3c.deadlockdebugger to figure out
> what the threads are doing at this time. Preferably, trigger the
> dump_threads() method of that module on SIGUSR1, like the
