solution RE: request.getSession() generates IllegalStateException in top filter(appears, response not being recycled properly if SocketException happenedfor it in the past)

I found a solution that seems to hold. Instead of associating ImageWriter directly with response.outputstream, I create temporary ByteInputStream that is associated with javax.imageio.ImageWriter Once imagewriter is done, I am dumping ByteInputStream bytes to response.outputsream. My

RE: request.getSession() generates IllegalStateException in top filter(appears, response not being recycled properly if SocketException happenedfor it in the past)

From: Leonard Gestrin [mailto:leonard.gest...@markettools.com] Subject: request.getSession() generates IllegalStateException in top filter(appears, response not being recycled properly if SocketException happenedfor it in the past) After a while, the same response object is being used by

RE: request.getSession() generates IllegalStateException in top filter(appears, response not being recycled properly if SocketException happenedfor it in the past)

Hi Chuck, I downloaded tomcat 6.0.18 and the problem still happens. The filter is not on the path to servlet that generates image; The problem with response being already committed happens in various places (in filter and in graph servlet itself on the subsequent calls). I can see that only