DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28331>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28331 Unpredictable switch from UTF-8 to other encoding in Response [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Minor |Normal Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-10-14 19:17 ------- Actually, I'm stupid, it's trivial, because I've already seen the bug. The problem is that your Java2D stuff you're using has some threading weirdness. So it accesses slightly asynchronously the response object, causing it to become committed during the start of the processing of the next request. The issue occurs when there are problems with the connection (IOE during rapid requests from client disconnects). So you have a bad servlet, and your bug is INVALID. Two solutions: a) Write to a buffer first (ie, if something bad happens, no harm done, since Java2D won't have any Tomcat object to mess with). b) Run the security manager (so that the facade objects get discarded to protect the integrity and isolation of requests). This will cause NPEs to be thrown during each invalid access. See, I told you it wouldn't be pretty for your issue ;) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
