Hi Rainer, > -----Original Message----- > From: Rainer Jung [mailto:rainer.j...@kippdata.de] > Sent: Thursday, July 14, 2011 12:17 AM > At least there was trouble about Java2D for several users in the past. > One such issue: > > https://issues.apache.org/bugzilla/show_bug.cgi?id=41772 > http://nerd.dk/blogs/bug-tomcat-or-java2d > > but you might find more. > > Regards, > > Rainer >
Thanks. In the meantime, I also came to that conclusion and replaced all instances of ImageIO.write(img, "PNG", response.getOutputStream()) in my servlets/webapps with something like ByteArrayOutputStream bout = new ByteArrayOutputStream(); ImageIO.write(img, "PNG", bout); bout.writeTo(response.getOutputStream()); so that the ImageIO never sees the real OutputStream, and it seems to work fine (no more IllegalStateExceptions or "wrong message format" errors in the isapi log when using AJP-APR). Is that a good practice (using ByteArrayOutputStream, then copy it to the response) to dynamically generate Images and serve them to the clients? Also, is there any hint to this on the Tomcat documentation/wiki? Because I don't think it would be unusual to dynamically generate images and serve them to clients using the ImageIO, and I think it could be a bit frustrating to find the actual problem if one doesn't know this. Thanks! Regards, Konstantin Preißer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org