https://issues.apache.org/bugzilla/show_bug.cgi?id=51813
--- Comment #2 from Christopher Schultz <ch...@christopherschultz.net> 2011-09-16 20:51:10 UTC --- There was a recent discussion on the users list where someone discovered that one of the JRE imaging APIs was keeping a reference to an OutputStream and randonly flushing it long after the request had completed. http://markmail.org/thread/pg6tcml5rvuiifv2 This wasn't causing crashes, though. I wonder if this might be a related problem: the output stream is flushed, but the response has already been sent and the thread/buffer put back into the worker queue. When another flush comes, it's in an invalid state? Mike, would you be willing to try to reproduce the problem and then wrap an OutputStream around the response's OutputStream, and pass THAT to the ImageIO? See here for an example of the kind of code I'm talking about: https://wiki.apache.org/tomcat/FAQ/KnownIssues#ImageIOIssues -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
