Jure -- What Zope are you using? what OS? which python? what machine? That information is need to help sort out the problem. Is this something that just started happening in a system that has been running for a while without a problem? Have you recently upgraded either Python or Zope? The exception happens in the guts of ZServer during a close when a unicode string is found on a fifo. I suspect that changing the test to allow ignore unicode stings as well as traditional strings would solve the problem, but I don't know the code well enough to say for certain. On Tue, 25 Nov 2003, Jure Koren wrote:
Has anyone seen this? I causes zope to just hang, and I don't have a clue as to where to start looking. It seems it happens within the ZServer, but I couldn't find a line in the entire tree of Zope that would assign a suspicious value to that 'p' variable. Can anyone suggest how to detect this and at least restart Zope, as this is causing us service outages (the question is really how to properly programatically restart Zope, as if you push Restart Zope within the control panel). Is killing -15 zope processes safe?