RE: [Zope] No stack trace returned on XMLRPC call
-----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Thursday, 29 August 2002 4:37 AM To: djay@avaya.com Cc: 'zope@zope.org' Subject: RE: [Zope] No stack trace returned on XMLRPC call
Jay, Dylan writes:
...
If this is two complex, make a specialized Python Script, that calls your Python script with the correct arguments. Call this (specialized) Python Script via HTTP.
If I could I would, but the arguments include lists of dictionaries which zope doesn't handle as normal http yet. Why do people not read my complete replies?
For your convenience, I stripped away the explanation for the simple case, because you are in the complex one.
Do you see now how to proceed?
Sorry, I did read both case but forgot to reply to the second. The reason I can't do the second is that I have about 1Mb of data in pickle in an external script that is trying to be uploaded. It's not a few simple arguments. I guess I could try incorporating my code into an external method and try it that way. Also of note I have tried using the medusa monitor unsuccessfully, gdb unsuccesfully, as well as the "run Zope in debug mode" like as done for unit testing... unsuccesfully. There always seems to be complications on a win32 platform. This post wasn't really about that however, I was more asking if anyone knew why no strack trace was being returned for the XMLRPC call, when under normal circumstances it is? Should I raise a bug for this?
Jay, Dylan writes:
... This post wasn't really about that however, I was more asking if anyone knew why no strack trace was being returned for the XMLRPC call, when under normal circumstances it is? Should I raise a bug for this? In Zope before 2.6, stack traces are badly integrated -- outside of the HTML tag. Many people complain that they are shown at all (because of security/privacy concerns).
It is quite natural that in the normal case (unless you are debugging), XML-RPC responses should not contain track traces as the XML-RPC client can not do much with them. I think, with Zope 2.6, you can much better control what happens with exceptions and the associated stack traces, at least for normal HTTP requests (not sure about XML-RPC, but hopefully there, too). You should be able to log the stack traces on the server and analyse them in the servers log file. Dieter
participants (2)
-
Dieter Maurer -
Jay, Dylan