[Zope] image upload

[Chris McDonough]

Hi Roman,

I believe the "accept" bug you're referring to may be due to a potential 
problem in the asyncore module that ships with Python 2.1.  In the past, 
Zope shipped with its own asyncore module, but when asyncore was updated 
in the Python core (in 2.1, I believe), we dropped our updated copy from 
  2.4.

If possible, I'd try placing a revision of the asyncore.py file into 
Zope's ZServer/medusa directory.  I'd try this one: 
http://cvs.zope.org/Zope/ZServer/medusa/Attic/asyncore.py?only_with_tag=Zope-2_3_3-src

Run for a while with that to see if the problem disappears.  Please let 
us know if it does or doesn't if you try it!

- C


Roman V. Isaev wrote:
> 	Ick. Ack. I've switched from zope's standalone webserver to
> apache + fastcgi + zope and so far it looks stable and doesn't 
> go wild with that accept error. But I stumbled on another problem --
> images do not upload correctly at all. Then stared apache at port 80 
> and zope at 8080. If I upload image through site:8080/manage interface
> it uploads fine. But if I upload image through site/manage (or my own 
> cgi form), image corrupts on the way! When I export both good and bad 
> images into xml format and diff them, these files are slightly different
> in binary part. What can corrupt image on its way through apache and 
> fastcgi? 
> 
> 	Of couse, it's easy to say use 8080 port to update the site. 
> Unfortunately, I can't run zope at 8080 port, because of previous
> bug with accept :( I can't find that bug because it happens only once in
> two or three days, only under normal conditions (i.e. I ran httperf and 
> put a big load on the site... everything worked okay, only to hang
> several hours later). And since my boss is very unhappy with webserver
> going down at odd hours when I'm unavailable, I can't really debug this
> situation :(
> 
> 


-- 
Chris McDonough                    Zope Corporation
http://www.zope.org             http://www.zope.com
"Killing hundreds of birds with thousands of stones"