Ian Maurer wrote: > Hello All, > > Thanks for all of your help so far. I did indeed have a mutex > problem in my code that caused some deadlock in my code. I replaced > the fcntl.flock calls with the lock in the threading module and that > seemed to do the trick. > > Now that I have that problem out of the way, I am pretty confident > that there is some sort of socket problem with that code in the > flush method of the TASASSStreamOut class (or at least that's where > the socket problem is showing up).
Is this problem still causing your appserver to lock up? Or is it just resulting in unusual messages in your logfile that you want to track down? My understanding of the code is that if the client is no longer listening, flush() will cause the "StreamOut Error" warning message to appear but will otherwise just be a no-op. Your servlet should go on processing, blissfully unaware that the client has disconnected. (It might make more sense for flush() to "raise EndResponse" at that point to keep the client from doing unnecessary additional processing. That would be a useful option to add to flush perhaps. It would also be useful for it to log a less alarming-looking error message.) - Geoff ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
