Webware for Python

> XMLRPCServlet internal error
> Traceback (most recent call last):
>   File "/usr/local/Webware-0.9.1/WebKit/XMLRPCServlet.py", line 46, in 
> respondToPost
>     params, method = xmlrpclib.loads(data)
>   File "/var/tmp/python2.3-2.3.4-root/usr/lib/python2.3/xmlrpclib.py", 
> line 1012, in loads
>     p.feed(data)
>   File "/var/tmp/python2.3-2.3.4-root/usr/lib/python2.3/xmlrpclib.py", 
> line 528, in feed
>     self._parser.Parse(data, 0)
> ExpatError: not well-formed (invalid token): line 17, column 29
Mark,

Your stack trace suggests that your problem may be with XMLRPC data that 
is being sent to you by somebody else---there may be nothing wrong with 
Webware.   I suggest that you hack XMLRPCServlet.py to output the 
contents of 'data' in the line identified in your trace.  Perhaps the 
problem will be obvious, or perhaps you can get whoever is sending the 
data to send simpler cases.  (e.g. XMLRPC has no representation of 
None/null, but some people use non-standard schemas to transmit it anyway.)


  Oliver

P.S. In the unlikely event that it's relevant, xmlrpclib in Python 2.2 
had a bug that produced a problem that looked something like this.  I 
don't remember the details, but I found an entry in my notes that says 
"fixed encoding for Fault".  Make of that what you will.

Mark Phillips wrote:
> I have rolled back to python 2.3.4, since Fedora Core 2 doesn't support 
> python 2.4.x. I ran my test suite. I am getting the following error. 
> This occurs once in a batch of requests, at about item 40 out of 100.

I'd like to figure out what's going wrong there. Can I have that test 
suite? Maybe I will add something similar to the standard Webware tests.

-- Christoph

On May 19, 2006, at 12:17 AM, Christoph Zwerschke wrote:

> Mark Phillips wrote:
>> I have rolled back to python 2.3.4, since Fedora Core 2 doesn't  
>> support python 2.4.x. I ran my test suite. I am getting the  
>> following error. This occurs once in a batch of requests, at about  
>> item 40 out of 100.
>
> I'd like to figure out what's going wrong there. Can I have that  
> test suite? Maybe I will add something similar to the standard  
> Webware tests.

I would be happy to share them, Christoph. Here is the problem: the  
python scripts I wrote to test the methods I wrote on top of Webware  
work fine. No errors.

It is only during the server-client dialog that the error is raised.  
So in this case, when I write about tests, I mean a script driving  
the client. the client is not written in python or some other open  
source code. This complicates passing it along due to the license of  
the vendor.

Nevertheless, I will keep this in mind and if I can figure how to  
package it properly, I will contribute it.

  - Mark

Thank you, Oliver. I will follow up on that idea.

And I vaguely recall reading about weakness in xmlrpclib, which why I  
posted these notes. My head hurts already, so if I have stumbled on  
to a known problem then I like to minimize the self-inflicted stress.

Mark

On May 19, 2006, at 12:11 AM, Oliver Bock wrote:

>> XMLRPCServlet internal error
>> Traceback (most recent call last):
>>   File "/usr/local/Webware-0.9.1/WebKit/XMLRPCServlet.py", line  
>> 46, in respondToPost
>>     params, method = xmlrpclib.loads(data)
>>   File "/var/tmp/python2.3-2.3.4-root/usr/lib/python2.3/ 
>> xmlrpclib.py", line 1012, in loads
>>     p.feed(data)
>>   File "/var/tmp/python2.3-2.3.4-root/usr/lib/python2.3/ 
>> xmlrpclib.py", line 528, in feed
>>     self._parser.Parse(data, 0)
>> ExpatError: not well-formed (invalid token): line 17, column 29
> Mark,
>
> Your stack trace suggests that your problem may be with XMLRPC data  
> that is being sent to you by somebody else---there may be nothing  
> wrong with Webware.   I suggest that you hack XMLRPCServlet.py to  
> output the contents of 'data' in the line identified in your  
> trace.  Perhaps the problem will be obvious, or perhaps you can get  
> whoever is sending the data to send simpler cases.  (e.g. XMLRPC  
> has no representation of None/null, but some people use non- 
> standard schemas to transmit it anyway.)
>
>
>  Oliver
>
> P.S. In the unlikely event that it's relevant, xmlrpclib in Python  
> 2.2 had a bug that produced a problem that looked something like  
> this.  I don't remember the details, but I found an entry in my  
> notes that says "fixed encoding for Fault".  Make of that what you  
> will.