Thanks for the ideas Jason, i actually just nailed the problem (after
troubleshooting along with a few other people for a few days)
I opened this bug for it (with a patch attached)
It's a problem in ThreadedAppServer keeping track of the # of bytes
remaining to be read from the socket, which is only apparent when
there is some delay in receiving data. (which for me means when webkit
and apache are on different servers). So that also explains why it was
On Tue, Jan 20, 2009 at 3:58 PM, Jason Hildebrand <jason@...> wrote:
> Hi Jehiah,
> Is this happening on some requests (occasionally), or on every request?
> If only occasionally, it's possible that some network tool or software is connecting directly to your appserver (on port 8080 or whatever you are using), and that the request is not coming via Apache. I've seen this happen; the solution is to firewall the appserver port so that is it only accessible on localhost (assuming apache and webware are running on the same host).
> Jason Hildebrand
> PeaceWorks Computer Consulting
> #2 - 396 Assiniboine Ave, Winnipeg
> 204 480 0314 --or-- 519 725 7875, ext 620.
> ----- "Jehiah Czebotar" <jehiah@...> wrote:
>> I'm in the process of upgrading to Webware 1.0 and when i'm trying
>> use webkit (via mod_webkit2) i get this error
>> File "/usr/local/Webware/WebKit/ThreadedAppServer.py", line 916, in
>> return loads(chunk)
>> EOFError: EOF read where object expected
>> I am only having this problem on some machines but i haven't been
>> to narrow down what is causing it. All configurations and libraries
>> seem to be the same.
>> If anyone on this list has any suggestions I'd appreciate it.