We disabled the keep alive connections and our problem is gone... Thanks guys
Tony 2008/7/4 Johnny Kewl <[EMAIL PROTECTED]>: > Tony... just another thought... > I want to change the philosophy a little.... > > If YOU open a stream... ie File f = new File.... Buffered streams etc... > Then make absolutey sure you close them... > > BUT.... > > If you GET a stream from TC... > ie > OutputStream out = response.getOutputStream(); > > DONT CLOSE IT... > > Its an issue we've had, but I didnt see it as a bug, just a feature ;).... > ie let TC decide when "it" wants to close its own streams. > > The theory I have on this is that if you bang the stream shut before all the > data is sent... you get the browser waiting for TC problem... and it only > shows itself under load... it seems. > > So its a little contradiction... close only YOUR streams... in theory this > is wrong I think, but TC checks it own buffers and will close them at some > stage... naturally the stream must not be in a global scope, or TC wont be > able to release it.... it doesnt feel good, but its worth a try... > > Ok... now I'm fresh out of guesses ;) > > --------------------------------------------------------------------------- > HARBOR : http://www.kewlstuff.co.za/index.htm > The most powerful application server on earth. > The only real POJO Application Server. > See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm > --------------------------------------------------------------------------- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
