Zope xmlrpc crashes without traceback
Hi. We are using a javascript xmlrpc(VCXMLRPC.js) library to essentially communicate with zope to retreive and display records in a browser. After a while, Zope just crashes without warning or any traceback of what caused the problem. It completely dies. When running in a command prompt, it dies silently as if the python interpreter crashed. We're running version 2.7 of zope with Python 2.3 on multiple window$ NT servers. Has anybody got a solution for this problem? -- G M S Software Factory Tel. +27 (11) 695 0400 x210 Fax +27 (11) 312 0265 Cell+27 (82) 770 7198 www.gmsonline.co.za <http://www.gmsonline.co.za/>
Herman Geldenhhuys wrote:
We are using a javascript xmlrpc(VCXMLRPC.js) library to essentially communicate with zope to retreive and display records in a browser. After a while, Zope just crashes without warning or any traceback of what caused the problem. It completely dies. When running in a command prompt, it dies silently as if the python interpreter crashed.
We're running version 2.7 of zope with Python 2.3 on multiple window$ NT servers.
Which minor version of Zope 2.7 do you run? There were package-problems with the python-xmlrpc-package in at least 2.7.0. -mj
In my control panel of the ZMI I get this: Zope Version : (Zope 2.7.2-0, python 2.3.4, win32) Python version: 2.3.4 (#53, May 25 2004, 21:17:02) [MSC v.1200 32 bit (Intel)] System Platform : win32 h Maik Jablonski wrote:
Herman Geldenhhuys wrote:
We are using a javascript xmlrpc(VCXMLRPC.js) library to essentially communicate with zope to retreive and display records in a browser. After a while, Zope just crashes without warning or any traceback of what caused the problem. It completely dies. When running in a command prompt, it dies silently as if the python interpreter crashed.
We're running version 2.7 of zope with Python 2.3 on multiple window$ NT servers.
Which minor version of Zope 2.7 do you run? There were package-problems with the python-xmlrpc-package in at least 2.7.0.
-mj
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
-- G M S Software Factory Tel. +27 (11) 695 0400 x210 Fax +27 (11) 312 0265 Cell+27 (82) 770 7198 www.gmsonline.co.za <http://www.gmsonline.co.za/>
Herman Geldenhhuys wrote at 2005-1-11 15:33 +0000:
We are using a javascript xmlrpc(VCXMLRPC.js) library to essentially communicate with zope to retreive and display records in a browser. After a while, Zope just crashes without warning or any traceback of what caused the problem. It completely dies.
Would you use a Unix flavour, I could tell you how you can get some information. But, I know little about Windows... Apparently, your Zope crashed. This usually happens in an C extension (memory corruption, bad pointer, range overflow, ...). Under Unix, I would attach Zope with a debugger and the debugger would get activated when the fatal event occurs. Maybe, Windows, too lets you run Zope in a C level debugger that gets control in case of fatal events ? -- Dieter
Dieter Maurer wrote:
Maybe, Windows, too lets you run Zope in a C level debugger that gets control in case of fatal events ?
Yep, if you have MSVC++ installed, you should get a modal dialogue box pop up when Zope crashes. However, I would stress that using runzope.bat in a command prompt is much more fruitful and finding out what kills things than usign Zope as a service. Hopefully the work Mark Hammond is doing on this will make things better eventually... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (4)
-
Chris Withers -
Dieter Maurer -
Herman Geldenhhuys -
Maik Jablonski