I thought I sent in a bug email to the list last week but I can't find it now. Anyway, I think it _might_ explain this problem. In ThreadedAppServer there is a generic exception handler around handleRequest that caught this problem when it happened but I don't know if it left the threads or sockets in a bad state.
The lines that call conn.recv, lines 351 and 361 and maybe others, don't have exception handlers and I saw them raise an error when the browser terminated the connection. The generic handler around handleRequest printed the error but conn.close() wasn't called as is normally the case. So, exception handling around the socket calls might solve the problem. -Jeff > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Geoff > Talvola > Sent: Monday, October 22, 2001 4:24 PM > To: Clark C . Evans; [EMAIL PROTECTED] > Subject: Re: [Webware-discuss] Webware death... > > > At 04:07 PM 10/22/01 -0400, Clark C . Evans wrote: > > >A tid bit of additional information. On Windows, with > >PythonWin 2.1 I get a "StreamOut" error in the log ... > >but the AppServer doesn't crash. > > On Windows, do you get a full traceback? If so, please > forward it to the list. > > To my ears it sounds like an exception handler is needed > around some socket > code to handle broken connections. > > > -- > > - Geoff Talvola > [EMAIL PROTECTED] > > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss > _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
