Hi all.

While using ab to perform stress tests on an application, I've run in
a situation where I have a "locked" Zope.

I installed DeadlockDebugger, and tried to have a dump from it, but it
is unable to answer, at leasts it seems to me.

So, I followed the recipe from ZopeLabs:


and got a traceback from gdb.

info threads gives the following:

* 5 Thread 0xb5b29b90 (LWP 17713)  0xffffe410 in __kernel_vsyscall ()
  4 Thread 0xb5322b90 (LWP 17714)  0xffffe410 in __kernel_vsyscall ()
  3 Thread 0xb4b21b90 (LWP 17715)  0xffffe410 in __kernel_vsyscall ()
  2 Thread 0xb4320b90 (LWP 17716)  0xffffe410 in __kernel_vsyscall ()
  1 Thread 0xb7d4b8c0 (LWP 17687)  0xffffe410 in __kernel_vsyscall ()

I'm including the traceback. As you can see, the last lines tell (for
all the threads) are:

  File "/var/local/zope28/base288/lib/python/Shared/DC/ZRDB/Results.py",
line 55, in __init__
    if n != name: aliases.append((n, SQLAlias(name)))
  File "<string>", line 1, in ?

Just one note: environment is Linux, Zope 2.8.8, python2.3

I understand Zope+python is quite old, so I'm just asking if there is
some "general" purpose advice on what to do in this case.


Marco Bizzarri

Attachment: tb
Description: Binary data

Zope maillist  -  Zope@zope.org
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to