Matt, your problem sounds like a simple timeout limitation. Which means itIt seems like it should be that simple, but I'm not sure that the appserver has any way of knowing that the client has "stopped". It's still probably trying to squirt the response back at apache, and the packets don't go anywhere. It seems to want to exhaust every packet, which for a 100M movie file is a lot.
should be possible to fix via a configuration value or similar.
This is probably more about apache (or whatever web server) that Ww itself.I assume Webware allows this in a global configuration, but it is also going to be useful to allow a very granular configuration of this to set in rare pages via the API. If these things are not possible, perhaps they should be.
I found a message from Geoff from a couple of years ago that references this problem:
----------------------
Clark,
I am unable to reproduce the "Webware death" problem at home on my Linux Mandrake 8.1 box. Whenever I cancel a long, large servlet prematurely, the exception handler get triggered due to the broken pipe, as you would expect. But nothing crashes.
The StreamOut Error: (10053, 'Software caused connection abort') message you see on Windows NT is also normal. In fact, the exception handler should be modified so that it simply ignores that message -- that's just what you get on Windows instead of EPIPE when the connection is canceled.
So I'm now 98% convinced that this is an OS bug, not a Webware bug or Python bug (I'm also using Python 2.1.1). I would suggest trying a newer version of Linux.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
